2010/7/1 Graeme Gregory <[email protected]>: > On Thu, 1 Jul 2010 13:52:26 +0200 > Frans Meulenbroeks <[email protected]> wrote: >> Net effect: either older versions are not updated, or the versions are >> updated but not tested. In both cases IMHO quality-wise a less >> desirable situation. >> >> Then again, I tried to fight the version diarrhea, and I lost.So be >> it. But don't come and ask me to improve the quality of recipes that >> IMHO should have been discarded long time ago. >> > Aaaaargh how many times do I have to say this, removing a recipe just > because it is old is not acceptable to me. Removing a recipe because > its discovered old versions are broken and no DISTRO is interested in > that old version is perfectly acceptable (as long as a strong > maintainer is kept in the loop if exists). > > Graeme
Graeme, I am aware of your position on this, and I am pretty sure you are aware of mine. However, for the rest of the world, I'd like to clarify things. Koen calls for action to move to new staging, BBCLASSEXTEND, nativesdk etc, which IMHO is a good action. However, if you want to keep older recipes this means that: - they need to be converted too - if they are converted one also need to test them if you are serious on quality if you want to, be my guest. I'm just saying that I'm not going to waste my time on this. Personally I feel that if we want to focus on quality we better remove the versions no one is interested in and focus our efforts, limited as they are, on the remaining recipes. And note that the old versions are still available in git. That is what revision control systems are for. Have fun! Frans _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
