2010/9/27 Mike Westerhof <m...@mwester.net>: > On 9/27/2010 1:19 AM, Frans Meulenbroeks wrote: >> 2010/9/26 Martin Jansa <martin.ja...@gmail.com>: >> >>> There was about ~1000 recipes failing to fetch few months ago, I don't >>> think this number is that much lower as I haven't seen any changes in >>> most of them. >>> >>> See my download status: >>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019206.html >>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-April/019234.html >> >> April is 5 months ago. Question is if it makes sense to keep recipes >> that are broken for > 5 months and no one who saw a need to fix them >> or complained about them. >> Personally I'm inclined to say it is a waste to spend any time on >> these. I would suggest moving them to e.g. nonworking but I guess the >> people who mix up quality and quantity will disagree on this. > > Mix up quality and quantity? That's a gross mischaracterization on your > part, and I quite resent it. > > There are valid reasons for some of those. If it is now necessary to > make Mr. Jansa like the comments on the ixp4xx firmware recipe in order > to keep the recipe in OE, I will update those. But I cannot make it so > that Intel will not require click-throughs in order to download the > firmware files. > > -Mike (mwester)
To clarify: Things that do not fetch because they require a manual download with accepting a license etc, I do not consider as broken. And of course we should keep these (I know the ixp4xx situation quite well). But how many of those do we have? I know about the ixp4xx and some ti ones. Maybe there are a few more that I missed but then again, most of the ~1000 recipes Martin mentioned and a lot of the recipes I listed above do not fall into this category but refer e.g. to a cvs server that is not there any more, to a version, tag or tarball that does not exist etc etc. For me those recipes are broken. And if it is a recipe that is broken for a prolonged amount of time, there is apparently no interest in it, and personally I would like to have this indicated one way or another, or, even better, move these recipes into a dedicated folder(like nonworking). In that case the recipe is still there should somebody be interested in it, but it does not clutter up the main recipe dir. (and note again that I feel things like the ixp4xx and the ti codecs etc do not fall into this group). And yes: we can also try to repair them by finding alternate sources etc (although this might be hard if someone changed from cvs to git). Then again if the recipe has been broken for a long time, without anyone taking action, filing a bug, reporting it on the list, I feel that there is not really interest in that recipe any more and personally I see it as a waste of time to try to repair them. Frans _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel