From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Ebuild removing
Date: Mon, 14 Mar 2005 22:17:01 +0000 [thread overview]
Message-ID: <20050314221701.79f25b29@snowdrop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
Ok, I dunno how many times me and Weeve have said this now, but it's
still being ignored...
FOLLOW THE FRICKIN' POLICY WHEN REMOVING EBUILDS
In particular:
1) Don't remove the highest stable version for any arch
2) Don't remove the highest ~arch version for any arch unless there is a
higher stable version for that arch. Exception: you're deliberately
forcing a downgrade because you committed something really broken to
~arch.
It really isn't funny when the arch teams have to spend more time fixing
screwups caused by developers not following keyword policy than working
on useful stuff. I don't care if being careful involves slightly more
work on your part -- identifying and fixing the screwups you caused not
only takes a lot more effort from a lot more people, it also impacts end
user systems. Stop being so damned rude.
--
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-03-14 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050314221701.79f25b29@snowdrop \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox