Summary: | repoman should prevent people from adding a new package with a metadata.xml pointing to maintained-needed directly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
2016-08-10 19:16:26 UTC
Sure it's possible! kill them with fire! ;) Just get a nod at least from council or consensus from -dev ml (like that is likely to ever happen) otherwise we'll probably not hear the end of the bitching why it is suddenly rejecting... I have just mailed council alias to try to know what do they think about the best option :/ If I understand correctly, this is already generally accepted as not allowed (see bug #591062 for example). Two notes: 1. This is probably unwanted for overlays where presumably packages don't have separate maintainers but all packages are handled by overlay owner. 2. The commit in question was not committed using repoman. Another note about the policies: https://bugs.gentoo.org/show_bug.cgi?id=591062#c5 (In reply to Brian Dolbec from comment #1) > Just get a nod at least from council We discussed this briefly during today's council meeting and agree that such a check is fine in repoman within existing policies. Thanks a lot for the really fast reply :) Please implement, removing council. repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist. |