| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi |
| 5 |
|
| 6 |
Is there currently any method for the retiring of old "versions" of |
| 7 |
gentoo? I am concerned that at some point in the future one of the |
| 8 |
package versions specified in /etc/make.profile/packages will be dropped |
| 9 |
from portage as a part of the progressive culling of older ebuilds that |
| 10 |
occurs over time. |
| 11 |
|
| 12 |
I've had a look at the packages files for versions 1.4 and 2004.0 and |
| 13 |
all of the packages have minimum specificed versions apart from |
| 14 |
<sys-apps/shadow-5, so it appears to be an unlikely event. That said, |
| 15 |
if it did occur, any site with a large installed base of gentoo machines |
| 16 |
could be in an awkward situation (particularly if packages are being |
| 17 |
distributed as binaries). |
| 18 |
|
| 19 |
Is there any policy/ideas/consensus among developers about how long a |
| 20 |
particular "version" will remain supported in portage? If not, it might |
| 21 |
be a useful idea to set sunset dates for particular "versions" of gentoo |
| 22 |
(as I doubt they are all going to be supported indefinitely). If there |
| 23 |
is a clear end date, it prevents anyone being caught out unexpectedly. |
| 24 |
|
| 25 |
Baz |
| 26 |
|
| 27 |
|
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFA5LhLJvZkjpKMF2wRAplBAJ49nBhKknalZLpNfkBPs1Gwl0d//QCgrTUo |
| 32 |
AHNqCCQ9D6Q0VcGQclLDqCQ= |
| 33 |
=byMR |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives