| 1 |
Some of you will remember me saying this before, but it wasn't a |
| 2 |
current topic at the time. So here it is again, now that everyone's |
| 3 |
talking about it. |
| 4 |
|
| 5 |
Gentoo is moving to 2004.1, 2004.2, 2004.3 style releases. This gives a |
| 6 |
working baseline for the stable trees that need to be supported. |
| 7 |
|
| 8 |
A new USE keyword (or profile) can be used to show which baseline the |
| 9 |
machine is following. For example, "2004.3-x86". This keyword, as "x86" |
| 10 |
and "~x86" already do, sets the version of the packages that are loaded |
| 11 |
into the system. |
| 12 |
|
| 13 |
The life-cycle of, for example, 2004.3-x86, would be: |
| 14 |
|
| 15 |
. |
| 16 |
. |
| 17 |
Current x86 profile copied to 2004.2-x86 |
| 18 |
2004.3 baseline released. |
| 19 |
x86 and ~x86 operate as they do now. |
| 20 |
. |
| 21 |
. <time passes> |
| 22 |
. |
| 23 |
Current x86 profile copied to 2004.3-x86 |
| 24 |
2004.4 baseline released. |
| 25 |
x86 and ~x86 operate as they do now. |
| 26 |
. |
| 27 |
. |
| 28 |
|
| 29 |
Over time, the older profiles can be tweaked to include security |
| 30 |
updates and minor version updates. This information will allow repoman |
| 31 |
to go through and cull out the distfiles and ebuilds that are no longer |
| 32 |
required by an aggregate of all profiles in use. |
| 33 |
|
| 34 |
Over time, the baseline profiles should merge to some degree as say, |
| 35 |
2004.1 and 2004.2 point to the same ebuilds for final releases of |
| 36 |
particular package versions. This will further diminish the amount of |
| 37 |
storage and processing that is required to support old Gentoo versions. |
| 38 |
|
| 39 |
-- |
| 40 |
steve@×××××××××××××××.au |
| 41 |
|
| 42 |
CRICOS Provider Number 00123M |
| 43 |
------------------------------------------------ |
| 44 |
This email message is intended only for the addressee(s) |
| 45 |
and contains information that may be confidential and/or |
| 46 |
copyright. If you are not the intended recipient please |
| 47 |
notify the sender by reply email and immediately delete |
| 48 |
this email. Use, disclosure or reproduction of this email |
| 49 |
by anyone other than the intended recipient(s) is strictly |
| 50 |
prohibited. No representation is made that this email or |
| 51 |
any attachments are free of viruses. Virus scanning is |
| 52 |
recommended and is the responsibility of the recipient. |
Archives