Hi!
From time to time i recognize that ebuilds are committed straight to
stable into the gentoo tree, especially for version bumps where no
changes in the ebuild are required. It also happens to me when providing
ebuilds via bugzilla!
So what about adding a repoman check to cover this. If a ebuild is
committed to the tree with stable keywords repoman could give a warning
about stable keywords in IUSE. I know there are cases where it is
necessary to commit an ebuild with stable keywords because of security
issues or others. But better be reminded about this than forgetting it.
I don't know if such a check already exists or is work in progress, i
have just found nothing comparable in repoman --help under QA keywords.
Any thoughts?
Regards,
Daniel
--
gentoo-dev@gentoo.org mailing list
From time to time i recognize that ebuilds are committed straight to
stable into the gentoo tree, especially for version bumps where no
changes in the ebuild are required. It also happens to me when providing
ebuilds via bugzilla!
So what about adding a repoman check to cover this. If a ebuild is
committed to the tree with stable keywords repoman could give a warning
about stable keywords in IUSE. I know there are cases where it is
necessary to commit an ebuild with stable keywords because of security
issues or others. But better be reminded about this than forgetting it.
I don't know if such a check already exists or is work in progress, i
have just found nothing comparable in repoman --help under QA keywords.
Any thoughts?
Regards,
Daniel
--
gentoo-dev@gentoo.org mailing list
