Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 3097

Summary: Portage doesn't handle new slotting properly
Product: Portage Development Reporter: Phil Bordelon (sunflare) <phil>
Component: UnclassifiedAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED FIXED    
Severity: major CC: phil, seemant
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Phil Bordelon (sunflare) 2002-05-27 22:35:29 UTC
I recently emerged links-2.0_rc4-r1 [after dealing with some back-and-forth with
gpm, etc.] and noticed that it installed just fine.  However, when I did a qpkg
-l links, I was presented with two different versions: the previous version and
the current one.  This would be fine, if the two versions didn't overwrite all
of the same executables.

After a bit of investigation, I discovered that the new ebuild has

SLOT="0"

and the old one doesn't.

I started digging through qpkg --installed, and I found a number of different
packages that have this problem.  The output of qpkg --installed --dups follows:

--
dev-libs/glib
dev-libs/openssl
gnome-extra/gnome-pilot
media-libs/freetype
media-libs/libdvdcss
media-libs/libdvdread
sys-apps/baselayout
sys-apps/shadow
sys-apps/util-linux
sys-libs/db
--

While some of these (freetype, glib) are intentional, others (util-linux,
libdvdread, shadow) are definitely not; by doing a qpkg -l on them, you can see
that they write all of the same binaries.

This is definitely confusing for the end-user, and makes for a somewhat mangled
portage database.

After looking at the suspect ebuilds, they all had a new

SLOT="0"

line in them, which seemed to cause the duplication.
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2002-05-28 05:13:36 UTC
Daniel, I was under the impression that if no SLOT is specified, portage assumes
SLOT="0" ?
Comment 2 Daniel Robbins (RETIRED) gentoo-dev 2002-06-02 20:56:33 UTC
Seemant: No, that is not the case.  With no slot, Portage assumes SLOT=""
(unslotted).
Comment 3 Phil Bordelon (sunflare) 2002-06-02 21:08:54 UTC
Then the ebuilds that have had 'SLOT="0"' added to them need to have that
removed, or some other solution needs to be done.  Else we're going to have
duplicate versions of all of these programs in our ebuild databases.
Comment 4 Daniel Robbins (RETIRED) gentoo-dev 2002-06-27 23:27:34 UTC
Apps should have SLOT="0"
Comment 5 Phil Bordelon (sunflare) 2002-06-28 00:14:57 UTC
Closing this out.  We've had enough discussions on this one, both on IRC and on
the mailing lists, to know that the current SLOT-based behaviour is what we want.