1 |
Stephen, |
2 |
|
3 |
Has this been implemented, or are you suggesting this? |
4 |
|
5 |
I definitely think that a stable tree needs to be established if we are to |
6 |
use gentoo successfully as servers. |
7 |
|
8 |
I like the idea, especially if each tree in maintained not with new packages |
9 |
like standard portage tree, but with security patches and fixes. |
10 |
|
11 |
Then if someone needs the features of a newer version, they can emerge it |
12 |
themselves and monitor updates for it as they go. |
13 |
|
14 |
Definitely a great idea I think. |
15 |
|
16 |
Chris |
17 |
|
18 |
-----Original Message----- |
19 |
From: stephen white [mailto:steve@×××××××××××××××.au] |
20 |
Sent: Thursday, 5 February 2004 12:26 PM |
21 |
To: gentoo-server@l.g.o |
22 |
Subject: [gentoo-server] Stable portage trees |
23 |
|
24 |
Some of you will remember me saying this before, but it wasn't a |
25 |
current topic at the time. So here it is again, now that everyone's |
26 |
talking about it. |
27 |
|
28 |
Gentoo is moving to 2004.1, 2004.2, 2004.3 style releases. This gives a |
29 |
working baseline for the stable trees that need to be supported. |
30 |
|
31 |
A new USE keyword (or profile) can be used to show which baseline the |
32 |
machine is following. For example, "2004.3-x86". This keyword, as "x86" |
33 |
and "~x86" already do, sets the version of the packages that are loaded |
34 |
into the system. |
35 |
|
36 |
The life-cycle of, for example, 2004.3-x86, would be: |
37 |
|
38 |
. |
39 |
. |
40 |
Current x86 profile copied to 2004.2-x86 |
41 |
2004.3 baseline released. |
42 |
x86 and ~x86 operate as they do now. |
43 |
. |
44 |
. <time passes> |
45 |
. |
46 |
Current x86 profile copied to 2004.3-x86 |
47 |
2004.4 baseline released. |
48 |
x86 and ~x86 operate as they do now. |
49 |
. |
50 |
. |
51 |
|
52 |
Over time, the older profiles can be tweaked to include security |
53 |
updates and minor version updates. This information will allow repoman |
54 |
to go through and cull out the distfiles and ebuilds that are no longer |
55 |
required by an aggregate of all profiles in use. |
56 |
|
57 |
Over time, the baseline profiles should merge to some degree as say, |
58 |
2004.1 and 2004.2 point to the same ebuilds for final releases of |
59 |
particular package versions. This will further diminish the amount of |
60 |
storage and processing that is required to support old Gentoo versions. |
61 |
|
62 |
-- |
63 |
steve@×××××××××××××××.au |
64 |
|
65 |
CRICOS Provider Number 00123M |
66 |
------------------------------------------------ |
67 |
This email message is intended only for the addressee(s) |
68 |
and contains information that may be confidential and/or |
69 |
copyright. If you are not the intended recipient please |
70 |
notify the sender by reply email and immediately delete |
71 |
this email. Use, disclosure or reproduction of this email |
72 |
by anyone other than the intended recipient(s) is strictly |
73 |
prohibited. No representation is made that this email or |
74 |
any attachments are free of viruses. Virus scanning is |
75 |
recommended and is the responsibility of the recipient. |