Am Dienstag, den 17.08.2010, 10:50 +0400 schrieb Roman I Khimov:
> В сообщении от Понедельник 16 августа 2010 23:35:59 автор Khem Raj написал:
> > IMO the newest version in a recipe should always be default preference
> > this way we can
> > stabilize recipe upgrades quicker. This also means a wider testing
> > before pushing a new recipe
> > DEFAULT_PREFERENCE = "-1" makes it to escape the testing.
> 
> Well, consider Perl, for example. Making 5.10.1 a default preference would 
> break binary packaged perl modules built for 5.8.8, so technically some 
> massive PR bump (most probably DISTRO_PR) is needed when updating to 5.10.1. 
> Forcing distro maintainers to do that is not nice, IMO.
> 
> Although the way it is now Perl 5.10.1 seems to be rarely used, which is also 
> not nice. Probably, there is no way to solve this problem for everyone. With 
> D_P it's not used much, removing D_P is asking for "YOU BROKE MY BUILD!!!" 
> love messages from random corners.

What about removing `DEFAULT_PREFERENCE = "-1"` and have the
distributions not wanting it pinning to the old version? This could be
done after a period of time after the push and an announcement to the
list asking what distribution prefers what and make that change in one
commit.


Thanks,

Paul

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to