From: Mike Myers <fluffymikey@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: KDE, metapackages, and monolithic packages
Date: Sun, 26 Feb 2006 17:05:57 -0600 [thread overview]
Message-ID: <44023455.3040906@gmail.com> (raw)
In-Reply-To: <pan.2006.02.26.10.52.26.601975@cox.net>
Duncan wrote
[deleted]
Thanks a lot for the detailed explanation.
Do you know if there's a way or going to be a way to handle the split
ebuilds so that reemerging or unemerging a split ebuild will reemerge or
unemerge the corresponding packages? It seems like the ebuilds are only
intended to make installing kde easier, which they do, but it doesn't
make handle uninstalling or reinstalling a split ebuild very easy at
all. Like, if I had kde 3.4 installed and upgraded to 3.5 and no longer
need 3.4, I can't just do 'emerge -C kde-meta-3.4', or something similar
if it's the installed with the split metapackage. Or if I just wanted to
remove some split ebuild, like say kdenetwork, but leave the rest, I
couldn't do 'emerge -c kdenetwork-meta' to uninstall the related packages.
Basically, my concern is that how KDE is installed is quite easily
handled, but uninstalling or reinstalling is not equally as easy, at
least in some aspects.
I hope I explain myself well enough, and thanks for your response.
Mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-26 23:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 8:32 [gentoo-dev] KDE, metapackages, and monolithic packages Mike Myers
2006-02-25 9:06 ` Diego 'Flameeyes' Pettenò
2006-02-25 18:33 ` Mike Myers
2006-02-25 18:44 ` Sebastian Bergmann
2006-02-25 18:45 ` John Myers
2006-02-25 20:07 ` Mike Myers
2006-02-25 20:15 ` Matthijs van der Vleuten
2006-02-26 10:52 ` [gentoo-dev] " Duncan
2006-02-26 23:05 ` Mike Myers [this message]
2006-02-27 0:56 ` Richard Fish
2006-02-27 10:09 ` Paul de Vrieze
2006-02-28 0:13 ` [gentoo-dev] " Duncan
2006-02-25 9:06 ` [gentoo-dev] " Petteri Räty
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=44023455.3040906@gmail.com \
--to=fluffymikey@gmail.com \
--cc=gentoo-dev@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