right now we're up to about 167 files in /usr/portage/licenses/ ... as i start making an ebuild for a new package i find its the GPL-2, with a *small* addition to it ... in reality i'm looking at adding *another* license file for such a small thing ... then i think, why do we even keep these in portage ? i doubt anyone has a packages installed that cover *every* license ... why not install said license when the ebuild installs ? we create like /usr/share/licenses/ ... we can maintain the common ones there ... when a new ebuild installs, it'll place its ebuild there as like /usr/share/licenses/${P} ... the only short coming i find is if the user wishes to read said license before emerging a package ... but maybe that can be handled in some way ?
*** Bug 38078 has been marked as a duplicate of this bug. ***
Hm, yes, I'd certainly like to see some better behavior for when an ebuild requires the user to accept a license manually (for instance, the quake3 ebuild). It's a bit annoying to come back to you computer in the morning and discover that, contrary to spending the night updating 100+ outdated packages on your box, it's been sitting there waiting for you to accept a license. A simpler solution for *that* particular case, would be to mark the ebuild requiring user input as interactive somehow, and then displaying a status to that effect when doing "emerge -p"... That way if you checked beforehand, you'd notice that an ebuild will need manual input, and you could deal with that one ahead of time. Then again, I suppose if it's only quake3 and a handful of others that have this restriction, it may not make sense to go mucking around in Portage, but it *is* rather annoying to find out you haven't been compiling all night...
I've said it before and I'll say it again, an ACCEPT_LICENSES feature in Portage would absoloutely rock. I would be cool if the default setting would only include licenSes which are compatible to the GPL. This would eliminate the need for the interactive accepting of license everytime you emerge packages like quake3(assuming ACCEPT_LICENSES contains Q3EULA), because you shouldn't have to accept it a million times, and it allows Portage to be more automatic. It would also be nice if someone added a global feature to Portage to ask the user if {s}he accepts the license of the package {s}he is about to merge if the license isn't in ACCEPT_LICENSES(and Portage adds the license to ACCEPT_LICENSES if the user accepts). This also made me think that there could be a REJECT_LICENSES variable, so if it contains Q3EULA, Portage will give an error if the user tries to merge it, or if the user tries to merge packages that depend on it.
the check_license function actually supports ACCEPT_LICENSE ... just put it in your make.conf and you wont be prompted by quake3 again ;)
*** Bug 46826 has been marked as a duplicate of this bug. ***
*** Bug 71834 has been marked as a duplicate of this bug. ***
This is intended for 2.1 afaik.
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Sorry for the bugspam, just some spring cleanin'
Duping against the later one because it has a patch, and I'm too lazy to move it ;) *** This bug has been marked as a duplicate of 17367 ***
