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