[oe] busybox recipe isappearances

Thomas Kunze thommycheck at gmx.de
Mon Oct 20 11:22:38 UTC 2008


Phil Blundell wrote:
> On Mon, 2008-10-20 at 00:02 +0200, Michael 'Mickey' Lauer wrote:
>   
>> Am Sunday 19 October 2008 19:46:55 schrieb Phil Blundell:
>>     
>>> It's long been my view that we should just add newer ones and leave the
>>> old ones alone.  There's really no reason to delete old recipes and,
>>> even if you check for PREFERRED_VERSIONs in the git tree, there is no
>>> real way to know who else might be relying on the version you are about
>>> to delete.
>>>       
>> That's true, however I always feel the urge of cleaning up when I see dozens 
>> or recipes for the same software [besides the amount of increased parsing 
>> efforts if we really were to keep everything). I'd rather have the rough 
>> guideline of keeping major (trusted) releases. At the end of the day, 
>> everything is in the archives.
>>     
>
> If parsing time were to become a big issue then one could imagine ways
> to solve that in bitbake.  For example, one could arrange for a command
> like "bitbake --disregard-old-versions" to parse all the files once,
> identify those versions which are older than the PREFERRED ones (whether
> set explicitly or automatically), and blacklist these old versions so
> that they are never parsed again.  The effect would be a bit like having
> an automatically-maintained BBMASK though of course the implementation
> would probably be slightly different.
>
> As for old versions being in the archives, that's true, but it seems
> like one could easily get into a kind of ping-pong thing where you
> delete an old version, I pull it out of the archives again, someone else
> now notices this "old cruft" and deletes it again, and so on.  I can
> imagine that being frustrating for all parties.
>   
This could be avoided if both parties would read the commit messages ;)
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   





More information about the Openembedded-devel mailing list