1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
| Interface? It wouldn't differ from how upgrades are currently performed. |
6 |
| |
7 |
| - Change your profile to a newer one |
8 |
The above step is the one that I see as unclear in the current system. |
9 |
| - emerge -pv system |
10 |
| - emerge -pv world |
11 |
| - modify make.conf, /etc/portage/* to taste |
12 |
| - and so on |
13 |
|
14 |
| Depends on how the package is versioned in the profile. E.g. if you have |
15 |
| glibc-2.3.2-r2 installed, and your profile has: |
16 |
| |
17 |
| =sys-libs/glibc-2.3.2 |
18 |
| |
19 |
| You will get glibc-2.3.2-r3 and any other updates, but not 2.3.3 or later. |
20 |
| If, for whatever reason, that release needs to be updated to 2.3.3, the |
21 |
| profile will need to be changed. Which is not an issue if there's a valid |
22 |
| reason why it needs to be done. |
23 |
Sounds reasonable to me. |
24 |
| |
25 |
| Cheers, |
26 |
| Dylan Carlson [absinthe@g.o] |
27 |
| Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F |
28 |
| |
29 |
| -- |
30 |
| gentoo-dev@g.o mailing list |
31 |
|
32 |
|
33 |
- -- |
34 |
Michael Marineau |
35 |
marineam@×××××××××.edu |
36 |
Oregon State University |
37 |
-----BEGIN PGP SIGNATURE----- |
38 |
Version: GnuPG v1.2.4 (GNU/Linux) |
39 |
|
40 |
iD8DBQFA/cG5iP+LossGzjARAg/KAJ4klnkIx1yi7+Laa6oQP/6owMv98wCfR7r8 |
41 |
hjgQUbBorkf0ikNyq4uuKo4= |
42 |
=ynP9 |
43 |
-----END PGP SIGNATURE----- |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |