| 1 |
On Monday, August 29 at 08:51 (+0000), Alan Mackenzie said: |
| 2 |
|
| 3 |
> What I really want to do is to try out Gnome 3, to see if it's like |
| 4 |
> what |
| 5 |
> people say it is, but without endangering my current Gnome 2.32.1. If |
| 6 |
> I |
| 7 |
> build Gnome 3, will its executable have a different name? |
| 8 |
|
| 9 |
It's not slotted, so that answers your first question. |
| 10 |
|
| 11 |
Also, gnome is a *bunch* of executables and libraries, so it's not as |
| 12 |
simple as renameing "gnome-session" to "gnome-session3". |
| 13 |
|
| 14 |
To answer the first, if you have two or more of the same package, say |
| 15 |
"foo", then slots tell portage that more than one version of "foo" may |
| 16 |
be installed if they are in different slots. For example, python-2.7.* |
| 17 |
packages are in slot "2.7" and python-3.2* packages are in slot "3.2" so |
| 18 |
python-2.7.2-r2 and python-3.2-r2 may be installed simultaneously. |
| 19 |
However, ex., 2.7.1-r2 and 2.7.2-r2 may not (because they are in both |
| 20 |
slot) "2.7". |
| 21 |
|
| 22 |
Similarly gnome-2* and gnome-3* (from the "gnome" overlay) are both in |
| 23 |
slot "2.0". |
| 24 |
|
| 25 |
The reason why GNOME 3 is in slot "2.0" is that it cannot be installed |
| 26 |
alongside GNOME 2, so no use in bumping the slot #. |
Archives