I'am often trying out the functionality of ebuilds out of the bugzilla but it's a little bit annoying to use an overlay system I manage by hand. Since gentoo portage have layman wouldn't it be a good idea to collect the ebuilds which are uploaded while bugfixing in an extra overlay? So taht anyone can just try out new ebuild that are trying to fix bugs? Reproducible: Always
This really doesn't have anything to do with portage proper. Aside from that, the idea isn't really feasible. Who do you propose manage this overlay? Doing it automatically introduces its own set of problems, such as knowing what package an ebuild is actually for and knowing which attachments from a given bug to actually pull down.
not to mention security problems associated with a no-authenticated upload and download cycle ...
(In reply to comment #0) > ... a good idea to collect the ebuilds which are uploaded while bugfixing in an extra overlay? > Actually, I like the idea of creating an extra overlay for 'bugzilla ebuilds' which aren't officially supported but an additional resource pool to choose from and an immense time-saver. I use or tried to use quite a lot of user made ebuilds related to 'mame' and especially 'mame frontends' and a few others, which weren't even available through the sunrise overlay. >Who do you propose manage this overlay? Maybe commit access only for registered gentoo bugzilla users? Those who are willing to upload their self-made ebuild to the provided overlay instead of only a attachment in bugzilla? I guess it remains the 'do it yourself' or maybe sunrise overlay method here ... especially with the security concerns.
OK, so basically this comes down to either automation (which is dangerous on the one hand and mostly useless on the other because of all the unwanted ebuilds with questionable QA you would get - and we have plenty of that in the tree already :) or handwork. In the latter case, it's probably best for each to do his or her own handwork. Since both options are unattractive, as they imply too little work and too much work respectively, I consider this idea thoroughly floated and duly shot down - there is no problem here for anyone to fix.
so i was walking on the streets today and realized that this was a problem. coming home, i looked if there already was a discussion about it and thereby ended up here. i have two tiny ideas: 1. maybe, instead of populating such an overlay, we should make a tiny tool which just takes an attachment number and automatically throws that into a local overlay. i guess it could also try to fetch patches. with an extra flag it starts emerging as soon as the ebuild is in the overlay 2. if the overlay should be populated, then maybe all packages in it should be masked and can be enabled in some way? maybe even in a similar manner as described before, ie all ebuilds are already in the tree, but all saved with an extra extension, for example foofox-1.6.ebuild.attachment.2874287, and some tool would move them to foofox-1.6.ebuild, and instantly start emerging. just syncing that bugzilla overlay would thus not provide you with direct access to ebuilds directly, but rather make it easier to start using them by already having them close. any ideas about this?
