From: "Albert W. Hopkins" <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How do slots work?
Date: Mon, 29 Aug 2011 07:40:59 -0400 [thread overview]
Message-ID: <1314618060.4107.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20110829085112.GA2908@acm.acm>
On Monday, August 29 at 08:51 (+0000), Alan Mackenzie said:
> What I really want to do is to try out Gnome 3, to see if it's like
> what
> people say it is, but without endangering my current Gnome 2.32.1. If
> I
> build Gnome 3, will its executable have a different name?
It's not slotted, so that answers your first question.
Also, gnome is a *bunch* of executables and libraries, so it's not as
simple as renameing "gnome-session" to "gnome-session3".
To answer the first, if you have two or more of the same package, say
"foo", then slots tell portage that more than one version of "foo" may
be installed if they are in different slots. For example, python-2.7.*
packages are in slot "2.7" and python-3.2* packages are in slot "3.2" so
python-2.7.2-r2 and python-3.2-r2 may be installed simultaneously.
However, ex., 2.7.1-r2 and 2.7.2-r2 may not (because they are in both
slot) "2.7".
Similarly gnome-2* and gnome-3* (from the "gnome" overlay) are both in
slot "2.0".
The reason why GNOME 3 is in slot "2.0" is that it cannot be installed
alongside GNOME 2, so no use in bumping the slot #.
next prev parent reply other threads:[~2011-08-29 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 8:51 [gentoo-user] How do slots work? Alan Mackenzie
2011-08-29 11:40 ` Albert W. Hopkins [this message]
2011-08-29 15:45 ` [gentoo-user] " walt
2011-08-29 16:02 ` Canek Peláez Valdés
2011-08-29 16:56 ` Albert W. Hopkins
2011-08-29 17:01 ` Canek Peláez Valdés
2011-08-29 18:26 ` Albert W. Hopkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314618060.4107.6.camel@localhost.localdomain \
--to=marduk@letterboxes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox