public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo or Linux from Scratch - Perspectives?
Date: Mon, 15 Aug 2005 11:27:28 +0100	[thread overview]
Message-ID: <20050815112728.4fe6489b@hactar.digimed.co.uk> (raw)
In-Reply-To: <1124099401.11891.9.camel@sf.rout.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]

On Mon, 15 Aug 2005 21:50:00 +1200, Nick Rout wrote:

> > I think some of this confusion is caused by the way people switch
> > between
> > two uses of the word stable. It can mean "doesn't crash", but then
> > most
> > upstream latest packages fit there, and some long standing releases
> > don't. It can also mean "not changing" and this is what some people
> > want
> > from a distribution. 
> 
> I think there is a third meaning with gentoo, namely when the ebuild is
> working well enough

This is not another meaning but a different context. People keep assuming
that the arch and ~arch alternatives refer to the package, when they only
refer to the ebuild.

> - this is independent of whether the upstream
> package is stable.(although it no doubt helps if it is). So you can have
> kde make a release (stable in their view) but gentoo takes some
> considerable time to make ebuilds that work acceptably, before they are
> marked stable (eg x86 cf ~x86)

It's not the time it takes to make them work acceptably, most of the KDE
3.4 ebuilds worked fine in the initial release. It is the time it takes
to prove that they are suitable for marking stable. The stable ebuild is
usually the same one that the ~arch users installed a month ago with no
problems.

Choosing between arch and ~arch is choosing whether you want someone else
to test things for you or whether you are prepared to do some of the work
yourself.


-- 
Neil Bothwick

Das Internet is nicht fuer gefingerclicken und giffengrabben. Ist easy
droppenpacket der routers und overloaden der backbone mit der spammen
und der me-tooen. Ist nicht fuer gewerken bei das dumpkopfen. Das
mausklicken sichtseeren keepen das bandwit-spewin hans in das pockets
muss; relaxen und watchen das cursorblinken.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-15 10:33 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 23:40 [gentoo-user] alsaconf not setting oss emulation Nick Rout
2005-08-06 23:59 ` [gentoo-user] SOLVED " Nick Rout
2005-08-07  0:30 ` [gentoo-user] " Christoph Eckert
2005-08-07  2:21   ` Nick Rout
2005-08-14 19:42 ` [gentoo-user] Gentoo or Linux from Scratch - Perspectives? Paul Hoy
2005-08-14 20:12   ` Zac Medico
2005-08-14 21:38     ` Nick Rout
2005-08-14 21:51       ` Holly Bostick
2005-08-14 22:48         ` Zac Medico
2005-08-14 23:28           ` Nick Rout
2005-08-14 23:46             ` Zac Medico
2005-08-15 10:59             ` fire-eyes
2005-08-15  0:53         ` Paul Hoy
2005-08-15  1:34           ` Holly Bostick
2005-08-15  1:53             ` Paul Hoy
2005-08-14 22:13       ` Joe Menola
2005-08-14 23:40         ` Nick Rout
2005-08-15  8:28           ` Neil Bothwick
2005-08-15  9:50             ` Nick Rout
2005-08-15 10:27               ` Neil Bothwick [this message]
2005-08-15 13:35             ` Paul Hoy
2005-08-14 22:35       ` Neil Bothwick
2005-08-15  1:08         ` Paul Hoy
2005-08-15  1:48           ` Zac Medico
2005-08-15  1:55             ` Joe Menola
2005-08-15  2:22               ` Paul Hoy
2005-08-15  2:20             ` Paul Hoy
2005-08-15  0:43       ` Paul Hoy
2005-08-14 23:42     ` Paul Hoy
2005-08-15 11:02     ` Graham Murray
2005-08-15 11:32       ` Zac Medico
2005-08-14 21:05   ` Joe Menola
2005-08-14 21:22     ` Neil Bothwick
2005-08-14 21:33       ` Joe Menola
2005-08-14 22:49         ` Paul Hoy
2005-08-14 21:37     ` Nick Rout
2005-08-14 21:52       ` Joe Menola
2005-08-14 22:43     ` Paul Hoy
2005-08-14 23:26       ` Joe Menola
2005-08-15  1:25         ` Paul Hoy
2005-08-14 21:24   ` Neil Bothwick
2005-08-15  0:37     ` Paul Hoy
2005-08-15  0:58       ` Holly Bostick
2005-08-15  1:39         ` Paul Hoy
2005-08-15  8:36           ` Neil Bothwick
2005-08-15  1:01       ` Zac Medico
2005-08-15  1:33         ` Paul Hoy
2005-08-15  8:18       ` Neil Bothwick
2005-08-15  9:06         ` Volker Armin Hemmann
2005-08-15  9:54           ` Neil Bothwick
2005-08-15 10:02             ` Volker Armin Hemmann
2005-08-15 10:29               ` Neil Bothwick
2005-08-15 10:54                 ` Zac Medico
2005-08-15  5:19   ` Walter Dnes
2005-08-15  6:22     ` Paul Hoy
2005-08-15 20:00   ` Peter Karlsson
2005-08-16  0:58     ` Paul Hoy
2005-08-16  1:11       ` Nick Rout
2005-08-16  1:56         ` Paul Hoy
2005-08-16  4:16           ` kashani
2005-08-16  4:23           ` Rumen Yotov
2005-08-21 20:05   ` Jerry McBride
2005-08-14 22:06     ` Volker Armin Hemmann
2005-08-15  0:56       ` Paul Hoy
2005-08-21 22:36       ` Jerry McBride
2005-08-14 23:32         ` Volker Armin Hemmann
2005-08-15  4:36         ` Barry.SCHWARTZ
2005-08-14 23:49     ` Paul Hoy
2005-08-15  8:31       ` Neil Bothwick

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=20050815112728.4fe6489b@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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