On 10/30/06, Jason Wever <[EMAIL PROTECTED]> wrote:
Please triple check what you want to commit and verify that you don't do
any of the following (which are punishable by death):
1) remove the last ebuild that is keyworded for a given arch, especially
when resulting in broken dependencies.
2) remove the last stable ebuild for an architecture
3) remove the last testing ebuild for an architecture when there is no
stable ebuild available after the removal
Consider yourself warned. Violation of any of these will cause the
jforman death goat squad to be dispatched to your location for a discreet
hit. For repeat offenders, public executions will be had, with Spanky
hosting.
1) Would it be a good idea for repoman to detect these when scanning
for QA issues ?
2) Would it be a good idea for repoman to alert QA (and possibly the
jforman death goat squad) in real time when a dev commits such
violations (and others) ? This could enable other devs to act right
away and avoid havoc to spread too far.
Denis.
--
gentoo-dev@gentoo.org mailing list