Gentoo Archives: gentoo-dev

From: Carsten Lohrke <carlo@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] summary: proposed solutions to arches/stable problem
Date: Wed, 23 Jun 2004 15:28:27
Message-Id: 200406231728.06839.carlo@gentoo.org
In Reply to: Re: [gentoo-dev] summary: proposed solutions to arches/stable problem by Jason Stubbs
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On Wednesday 23 June 2004 15:37, Jason Stubbs wrote:
5 > On Wednesday 23 June 2004 19:53, Paul de Vrieze wrote:
6 > > I think that before this all, we first and all need to get absolutely
7 > > clear what we want to do with these keywords. As a package maintainer I
8 > > know that it can sometimes be displeasing when other archs mark your
9 > > package as stable. I do however not think that we need to spend that much
10 > > effort on the problem.
11 > >
12 > > If we want to spend the effort we however should first make clear the
13 > > purpose, not just make clear what the arch maintainer's keyword is
14 > > without making it clear what is the purpose of this knowledge.
15 >
16 > That's probably the most rational thing I've heard in this entire debate -
17 > not that it has all been irrational...
18 Right. When I wrote the email, which was followed by Aron's with his "stable"
19 keyword idea, I had something else in mind. One point is, that Ciaran and
20 Travis rather aggressive defend the status quo to be able to declare some
21 ebuild stable on a specific arch (Please don't hack on me you two, I'm just
22 stating not assessing it.). So all discussed ideas try to avoid these
23 communication problem and to allow different development speeds on different
24 architectures and weaken the role of the package maintainer. I consider this
25 not a bad thing for fast evolving architectures , but it may cause other
26 problems, like comparable and interoperable releases* on all supported
27 architectures.
28
29 * I know that we don't really have releases, but don't forget there are
30 thoughts about enterprise Gentoo and that not the always evolving nature of
31 Gentoo will be measured from outside, but 200X.Y releases.
32
33
34 Carsten
35 -----BEGIN PGP SIGNATURE-----
36 Version: GnuPG v1.2.4 (GNU/Linux)
37
38 iD8DBQFA2aGGVwbzmvGLSW8RAhyqAKCLnOtHMLCaM1/iHV7Xo8ZbzbZ8cgCdFV5y
39 Z8j/R/GIhpFdDZo2P7m943w=
40 =O9Hr
41 -----END PGP SIGNATURE-----
42
43 --
44 gentoo-dev@g.o mailing list