From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Reworking package stabilization policies
Date: Sat, 27 Mar 2010 23:34:43 -0700 [thread overview]
Message-ID: <20100328063443.GA25918@hrair.hsd1.ca.comcast.net> (raw)
In-Reply-To: <201003281931.10274.ali_bush@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Sun, Mar 28, 2010 at 07:31:10PM +1300, Alistair Bush wrote:
> > On Saturday 27 of March 2010 21:58:41 William Hubbs wrote:
> >
> > It's really freaking silly to wait months for stabilization of some random
> > php/perl library that's known to work.
>
> Have you ever just considered closing the stabilization bug and ignoring the
> arch. If they take so long to mark your packages as stable why do you care
> about them enough to even attempt to stabilize anything on their arch.
If the pkg isn't a leaf node, you wind up keeping older and older
versions lingering across multiple pkgs to keep it from breaking
stable.
This is assuming that it's still heavily frowned upon to remove the
only stable version available for a non-dead arch...
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-28 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 20:58 [gentoo-dev] reminding slacker arch's to handle bugs William Hubbs
2010-03-28 5:47 ` [gentoo-dev] [RFC] Reworking package stabilization policies Maciej Mrozowski
2010-03-28 6:31 ` Alistair Bush
2010-03-28 6:34 ` Brian Harring [this message]
2010-03-28 6:56 ` Alistair Bush
2010-03-28 9:43 ` [gentoo-dev] " Duncan
2010-03-28 20:35 ` [gentoo-dev] " William Hubbs
2010-03-28 7:39 ` Ciaran McCreesh
2010-03-28 10:04 ` Tomáš Chvátal
2010-03-28 11:32 ` Richard Freeman
2010-03-28 15:18 ` Maciej Mrozowski
2010-03-29 7:30 ` Peter Volkov
2010-03-29 17:10 ` Maciej Mrozowski
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=20100328063443.GA25918@hrair.hsd1.ca.comcast.net \
--to=ferringb@gmail.com \
--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