Enhancement Request. Need a new make.config keyword to allow more control over what is put into /usr/portage. I'm asking for a new keyword in make,config. The idea being... an intelligent way to filter what is being maintained in /usr/portage. Currently, everything and the kitchen sink is in /usr/portage/. A new keyword, say "x86-linux" would restrict emerge --sync to only consider ebuilds that are stable for the linux platform. Thus no testing ebuilds, patches and above all else no bsd and any other non-linux stuff would be put into /usr/portage. The benefit would be three fold... 1 - a much smaller /usr/portage tree 2 - a much more snappier portage process 3 - BEST OF ALL... simpler and shorter sync sessions with the Gentoo servers... The "x86-linux" could be expanded to "~x86-linux" and "x86-bsd", "~x86-bsd" and so on... In my best guess... I don't need or use nearly two thirds of what is in my portage tree on my x86 server... Why must we maintain what we don't use? It's time to fix this. Also... it'd be a good time for a switch that would enable/disable keeping multiple versions of ebuilds. If I'm running an x86 (stable) server, why on earth are we required to maintain several x86 versions of the ebuilds? Thank you, for your time and Merry Christmas. Reproducible: Always
There is only few packages that are not intended for x86/amd64 IMO, so your particular example doesn't hold. Only the minorities (bsd, hppa, etc.) would benefit from your idea. However, it should be implemented server side, which IMO is a disadvantage which is bigger than the intended benefits for the users.
(In reply to comment #0) > The idea being... an intelligent way to filter what is being maintained in > /usr/portage. The most practical way to do this is to allow the dependency metadata to be fetched separately from whole ebuild. That way, you can calculate which ebuilds to fetch and only fetch the ones that are needed. This idea is discussed here: http://en.gentoo-wiki.com/wiki/Google_Summer_of_Code_2010_ideas#Cache_sync http://en.gentoo-wiki.com/wiki/Google_Summer_of_Code_2010_ideas#Repository_of_Self-Contained_Ebuild_Source_Packages
*** Bug 351808 has been marked as a duplicate of this bug. ***
Nothing done with my original request, Can soeone close this?
It might still get implemented someday: http://wiki.gentoo.org/wiki/Google_Summer_of_Code/2012/Ideas#Repository_of_self-contained_ebuild_source_packages If bugzilla still had the resolved:later resolution, then I'd probably choose that.
