public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What happens with masked packages?
Date: Sat, 25 Feb 2006 13:34:28 -0600	[thread overview]
Message-ID: <200602251334.28098.bss03@volumehost.com> (raw)
In-Reply-To: <20060225185728.110b3398@snowdrop.home>

On Saturday 25 February 2006 12:57, Ciaran McCreesh <ciaranm@gentoo.org> 
wrote about 'Re: [gentoo-user] What happens with masked packages?':
> On Fri, 24 Feb 2006 14:57:43 -0600 "Boyd Stephen Smith Jr."
>
> <bss03@volumehost.com> wrote:
> | > ~arch means a package is a candidate for going into arch after
> | > further testing, if said testing does not turn up new bugs. This
> | > means that both the ebuild *and* the package should be likely to be
> | > stable.
> |
> | So, betas shouldn't ever be ~arch?  Or is your definition of stable
> | broad enough to include betas?
>
> Entirely dependent on the upstream. I've had Vim beta releases in
> ~arch, for example, because I'm confident in upstream's ability to do
> beta releases without screwing up.

So, it's based on the collective opinion of the gentoo developers?  
Wouldn't it be better to put that in the hands of the gentoo user?

> The -* abuse is one of the many things on QA's list of "stuff we want
> to get fixed". However, it's considered extremely low priority on
> existing packages.

As it should be, since there are well-known user work-arounds.

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-25 19:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 19:55 [gentoo-user] What happens with masked packages? Thierry de Coulon
2006-02-22 20:02 ` Dave Nebinger
2006-02-22 20:38   ` Thierry de Coulon
2006-02-22 21:38     ` Rafael Bugajewski
2006-02-22 22:12     ` Boyd Stephen Smith Jr.
2006-02-22 22:44       ` Dave Nebinger
2006-02-22 22:53       ` Thierry de Coulon
2006-02-22 23:08         ` Boyd Stephen Smith Jr.
2006-02-24 17:31       ` Ciaran McCreesh
2006-02-24 20:57         ` Boyd Stephen Smith Jr.
2006-02-25 18:57           ` Ciaran McCreesh
2006-02-25 19:34             ` Boyd Stephen Smith Jr. [this message]
2006-02-25 23:47               ` Mariusz Pękala
2006-02-26  5:16                 ` Boyd Stephen Smith Jr.
2006-02-26 16:34                   ` Mariusz Pękala
2006-02-26 17:06                   ` Bo Andresen
2006-02-26 20:40                     ` Boyd Stephen Smith Jr.
2006-02-26 23:25                       ` John J. Foster
2006-02-27  0:15                       ` Bo Andresen
2006-02-27  0:57                         ` Boyd Stephen Smith Jr.
2006-02-27  3:44                           ` Zac Slade
2006-02-26 16:11               ` Ciaran McCreesh
2006-02-26 23:29                 ` John J. Foster
2006-02-27  0:11                   ` Ciaran McCreesh
2006-02-27  1:26                     ` John J. Foster
2006-02-27 17:17                       ` Ciaran McCreesh
2006-02-27 17:33                         ` Dave Nebinger
2006-02-27 18:51                           ` Ciaran McCreesh
2006-02-22 21:27 ` Boyd Stephen Smith Jr.

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=200602251334.28098.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --cc=gentoo-user@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