From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading KDE
Date: Sun, 31 Jul 2005 16:52:21 -0700 [thread overview]
Message-ID: <42ED6435.7060809@gmail.com> (raw)
In-Reply-To: <200507311929.19587.gentoo.org@machturtle.com>
David Corbin wrote:
> On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote:
>
>>On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote:
>>
>>>root@Merlin:/# emerge --pretend kde-meta
>>>
>>>These are the packages that I would merge, in order:
>>>
>>>Calculating dependencies ...done!
>>>[blocks B ] =kde-base/kdebase-3.4* (is blocking
>>>kde-base/kscreensaver-3.4.1)
>>
>>You currently have KDE installed with the monolithic ebuilds. to stay
>>with them, use "emerge -av kde" instead of kde-meta (there's not a lot of
>>point in using the split ebuilds if you're going to install everything
>>anyway). Alternatively, you'll have to unmerge that various kdebase, and
>>probably some of the other monolithic ebuilds, before merging kde-meta.
>>Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds
>>you use.
>
>
> What's the best way to find out what all the "split ebuilds" are?
>
> David
The kde-meta ebuild should cover all of the split ebuilds. If you read that you will discover that it depends on other meta packages. Read the ebuilds of those meta packages to find out what they depend on, and so on.
$ equery which kde-meta
/usr/portage/kde-base/kde-meta/kde-meta-3.4.2.ebuild
Unfortunately, equery depgraph does not seem to be very helpful for this type of query.
Zac
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-31 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 21:28 [gentoo-user] Upgrading KDE Daniel D Jones
2005-07-31 21:47 ` Zac Medico
2005-07-31 21:59 ` Neil Bothwick
2005-07-31 23:29 ` David Corbin
2005-07-31 23:52 ` Zac Medico [this message]
2005-08-01 7:40 ` Neil Bothwick
2005-08-02 9:08 ` Fernando Meira
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=42ED6435.7060809@gmail.com \
--to=zmedico@gmail.com \
--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