Re: [Chicken-hackers] Should we make a 4.12 release?

[Mario Domenech Goulart]

Hi,

On Tue, 03 Jan 2017 23:50:19 +0100 address@hidden wrote:

>> On Tue, 03 Jan 2017 21:35:46 +0100 address@hidden wrote:
>> 
>> >> Salmonella relies on -prefix to install eggs into a fresh local egg
>> >> repository.  That's how it is able to catch dependency problems, for
>> >> example.
>> >
>> > Shouldn't you use a separately built chicken insallation for that,
>> > with a pristine egg repository for each run?
>> 
>> That would work, but it would make the use of salmonella very
>> inconvenient, as salmonella would depend on a fresh chicken installation
>> to work.  Not sure if I understand your proposal correctly, though.
>> 
>> For example, we have two common scenarios where salmonella is used:
>> 
>> * by egg authors, to test eggs:
>> 
>>   $ cd egg-source-dir
>>   $ salmonella
>> 
>> * by our test farm, where we build the whole set of eggs for different
>>   combinations of chicken branches, C compilers, etc.
>> 
>> Would it be feasible to use salmonella and C5 in these cases?
>
> I think it would. To truly test in a clean environment I would suggest to
> use a fresh chicken installation for case 1 as well. Note that this can
> be done by pure copying/hardlinking of files, assuming the user didn't
> modify installed files. But I didn't know of case 1 and am not sure what
> advantages it provides.

Case 1 is the recommended check before one submits an egg to the egg
index.  It detects dependency problems, malformed .meta fields, runs
tests etc.  Basically, all the checks that are performed daily to all
eggs, but _before_ eggs are published.  That saves us from reporting
trivial bugs right after eggs are added to the coop and guarantees that
eggs can be at least installed when they are available from the official
egg index.

All the best.
Mario
-- 
http://parenteses.org/mario