public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] When a package is marked as stable or not?
Date: Wed, 22 Aug 2018 09:17:00 -0400	[thread overview]
Message-ID: <CAGfcS_kP7e9n1mBA2nDLCzRABoL49k+8-bOH6BdMY_-efFBvRQ@mail.gmail.com> (raw)
In-Reply-To: <20180822120209.l766tnjnidqgcuet@mew.swordarmor.fr>

On Wed, Aug 22, 2018 at 8:02 AM Alarig Le Lay <alarig@swordarmor.fr> wrote:
>
> I’m a little curious about the way a package is considered as stable or
> ~arch.
>

Packages always start out in ~arch and sometimes become stable.  A
package version CAN be made stable if:
1.  It has been in ~arch for 30 days (exceptions made for security fixes)
2.  It has no major problems
3.  It works when built/run against stable dependencies.

Now, not every package that CAN be made stable actually gets marked
stable.  Half of this is the same reason that lots of desirable things
don't happen - people don't get around to it.  The other half are
situations where the maintainer doesn't think that it makes sense to
stabilize a package, usually for reasons you'd probably agree with.

If a package already is stable, then at one point in time it probably
worked fine.  It would only lose the stable keyword if it had a fairly
serious problem and it wasn't likely to get solved.  I couldn't really
speak to the current state of libreoffice-bin, but for most of its
history the binary openoffice packages have been problematic, but of
course popular.  In some sense stable is a relative term - it may be
desirable to offer both a stable and testing version of openoffice-bin
so that users who want to use it don't have to run bleeding-edge, even
if neither is as stable as the from-source version.

Also, a lot of bugs are somewhat situational.  Something that you
consider critical might not be serious to somebody else.  If the
stable version works as well as the versions marked as ~arch then
there is little benefit to dropping the stable keyword, since users
STILL will have to deal with the issue, and now they might have to
deal with other issues as well.

I guess to sum up you could say that the stable version of a package
has received more testing than an unstable version OF THE SAME
PACKAGE.  There are no promises that a stable version of one package
is comparable to a stable version of a different package.

Finally, I'll note that if you ask 10 Gentoo users/devs what they
think stable ought to be, you'll probably get at least half a dozen
answers, so the above is meant more as a description of the status quo
than anything else.

-- 
Rich


  reply	other threads:[~2018-08-22 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 12:02 [gentoo-user] When a package is marked as stable or not? Alarig Le Lay
2018-08-22 13:17 ` Rich Freeman [this message]
2018-08-22 14:24   ` Alarig Le Lay
2018-08-22 17:43     ` Mick

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=CAGfcS_kP7e9n1mBA2nDLCzRABoL49k+8-bOH6BdMY_-efFBvRQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --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