From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: unmerging slotted group packages
Date: Mon, 29 Jan 2007 12:03:28 +0000 (UTC) [thread overview]
Message-ID: <epknqf$ctt$3@sea.gmane.org> (raw)
In-Reply-To: 200701291131.54208.bo.andresen@zlin.dk
Bo Ørsted Andresen <bo.andresen@zlin.dk> posted
200701291131.54208.bo.andresen@zlin.dk, excerpted below, on Mon, 29 Jan
2007 11:31:46 +0100:
> I didn't really have the patience to read all the way through your post but
> this part does appear to be incorrect.
>
> The world file can only contain package names (neither slots nor versions) so
> removing kde-3.4 while keeping kde-3.5 is not going to change what's in the
> world file. If something in the world file depends on kdelibs-3.5 then
> `emerge --depclean` will not remove kdelibs-3.4 or any other old slots that
> really aren't needed anymore.
>
> Only --prune or --unmerge will do that and both of those currently have the
> downside that they don't check whether it's still needed (as in the case of
> autoconf, automake etc.). Implementing a safer --prune reusing some of the
> code from --depclean (which was improved a lot in portage-2.1.1) has been
> discussed in the past but it isn't done yet.
Thanks for the correction. While I knew that world doesn't contain slots
or versions, I thought (and believe it works that way in ~portage, but it
may not have reached stable yet, and I could be wrong) that unmerging the
metapackage would then release the dependency on the other stuff in that
slot. For KDE monolithics, for instance, I believe(d) that while
old kdelibs won't be unmerged immediately as it isdepended on by
kdebase which is depended on by (among others) kdegraphics, without the
old kde-3.4.x, kdegraphics-3.4.x would be trimmed by --depclean, and once
all the other kdewhatever-3.4.x packages had been trimmed, then
kdebase-3.4.x could be trimmed, and then kdelibs-3.4.x.
However, I'm using the split packages, not the monolithics, and don't have
kde-meta merged as I don't need all the split packages either. That makes
it harder to test. In addition, I unmerge old versions pretty quickly
once I've upgraded and found no critical non-working stuff (like say
konqueror or kmail, or anything having to do with the ability to run a KDE
desktop itself), keeping up with that system maintenance, so I've never
gotten to the point of having that much cruft to unmerge at once. Thus,
that part wasn't tested, and you (naturally) had to call me on it. =8^)
Still, genuinely, thanks, as if I'm not called on such things, I get lax,
and it's those I'm trying to help that get hurt, so I'd much rather get
called on my errors than not!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-29 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 5:17 [gentoo-amd64] unmerging slotted group packages Daiajo Tibdixious
2007-01-28 10:46 ` Neil Bothwick
2007-01-28 11:19 ` Peter Humphrey
2007-01-28 11:55 ` Richard Freeman
2007-01-28 12:07 ` Peter Humphrey
2007-01-28 12:10 ` Daiajo Tibdixious
2007-01-28 12:16 ` [gentoo-amd64] " Duncan
2007-01-28 21:02 ` Steve Herber
2007-01-28 23:48 ` Daiajo Tibdixious
2007-01-29 11:47 ` Duncan
2007-01-29 12:16 ` Neil Bothwick
2007-01-29 10:31 ` Bo Ørsted Andresen
2007-01-29 12:03 ` Duncan [this message]
2007-01-29 22:38 ` Bo Ørsted Andresen
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='epknqf$ctt$3@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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