On Fri, 17 Nov 2006 22:37:43 +0100, Hisham Muhammad <[EMAIL PROTECTED]>  
wrote:

> On 11/17/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
>> There was no good announcement (if there was none I must have missed it)
>> that it was mandatory to use the new format of dependencies if versions
>> were to be complied with. I also thought that there _might_ be people
>> still using old versions of Compile, which uses Dependencies (and/or old
>> versions of scripts) and I wanted to create as compatible recipes as
>> possible (using new format would break the recipes for them).
>
> For this particular problem, the compile_version variable works well  
> enough,
> warning that a recipe was designed to a more recent version of Compile.
>
Yes, I know. I was just overly causious and as I wasn't aware of the new  
format I thought that it wouldn't do any harm.

>> André wrote:
>> > The question is:
>> > Should we keep dropping the version number of old-style dependencies
>> > lines for recipes? Or should we rollback and interpret "Program X" as
>> > "Program >= X" (like it is being done with binary packages)?
>> >
>> I think so, at least during a transition period. As it's implemented  
>> right
>> now many recipe are broken on many systems as they might have an earlier
>> version of the program installed and then CheckDependencies "think it's
>> ok", even if the recipe requires a higher version. In the meantime
>> RecipeLint (GenRecipeStore uses RecipeLint) would give an error if not  
>> the
>> new format was used and Compile would use GenRecipeStore to pack the
>> recipe, instead of a single tar operation (the last change I'll  
>> implement
>> in a couple of minutes). In a couple of months enough recipes have been
>> updated to drop the compability code (if it's even necesary)
>
> For new recipes, I think it's better to use ">=", "=", etc. explicitly
> and use the
> "compile_version" variable to instruct users to upgrade.
>
Yes, for new recipes I think that's the way to go. That's what I was after  
when I said that Compile should use GenRecipeStore (which uses RecipeLint  
on the recipe), to "force" users to use the new format. But how about the  
~3800 recipes in the store (of which at least a couple of hundred at least  
are highly expected to be used)?

-- 
/Jonas

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to