Gentoo Archives: gentoo-dev

From: stephen white <steve@×××××××××××××××.au>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: GLEP 19 -- Gentoo Stable Portage Tree
Date: Mon, 09 Feb 2004 09:17:07
Message-Id: B9A679E2-5AE0-11D8-951D-000393B7D972@cs.adelaide.edu.au
In Reply to: Re: [gentoo-dev] RFC: GLEP 19 -- Gentoo Stable Portage Tree by Chris Gianelloni
1 On 04/02/2004, at 1:58 AM, Chris Gianelloni wrote:
2 > db-4.1.25_p1-r3 KEYWORDS="ia64 ppc amd64 ppc64 hppa"
3 > db-4.0.14-r2 KEYWORDS="x86 sparc alpha mips"
4
5 Reposted from gentoo-server:
6
7 Gentoo is moving to 2004.1, 2004.2, 2004.3 style releases. This gives a
8 working baseline for the stable trees that need to be supported.
9
10 A new profile can be used to show which baseline the machine is
11 following. For example, "2004.3-x86". This profile (or USE keyword), as
12 "x86" and "~x86" already do, sets the version of the packages that are
13 loaded into the system.
14
15 The life-cycle of, for example, 2004.3-x86, would be:
16
17 .
18 .
19 Current x86 profile copied to 2004.2-x86
20 2004.3 baseline released.
21 x86 and ~x86 operate as they do now.
22 .
23 . <time passes>
24 .
25 Current x86 profile copied to 2004.3-x86
26 2004.4 baseline released.
27 x86 and ~x86 operate as they do now.
28 .
29 .
30
31 Over time, the older profiles can be tweaked to include security
32 updates and minor version updates. This information will allow repoman
33 to go through and cull out the distfiles and ebuilds that are no longer
34 required by an aggregate of all profiles in use.
35
36 Over time, the baseline profiles should merge to some degree as say,
37 2004.1 and 2004.2 point to the same ebuilds for final releases of
38 particular package versions. This will further diminish the amount of
39 storage and processing that is required to support old package
40 versions.
41
42 --
43 steve@×××××××××××××××.au
44
45 CRICOS Provider Number 00123M
46 ------------------------------------------------
47 This email message is intended only for the addressee(s)
48 and contains information that may be confidential and/or
49 copyright. If you are not the intended recipient please
50 notify the sender by reply email and immediately delete
51 this email. Use, disclosure or reproduction of this email
52 by anyone other than the intended recipient(s) is strictly
53 prohibited. No representation is made that this email or
54 any attachments are free of viruses. Virus scanning is
55 recommended and is the responsibility of the recipient.
56
57
58 --
59 gentoo-dev@g.o mailing list