From: "Brett I. Holcomb" <brettholcomb@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Is there and Alternative to compiling kde?
Date: Sat, 10 Dec 2005 11:49:11 -0500 [thread overview]
Message-ID: <200512101149.11364.brettholcomb@bellsouth.net> (raw)
In-Reply-To: <uwticncbl.fsf@newsguy.com>
Did you check out the Gentoo docs on kde split ebuilds? It has a lot of good
info. I started to emerge with the kde and then decided to go with the meta
so per the instructions I had to remove some stuff - it shows up as blocked.
On Saturday 10 December 2005 11:31, Harry Putnam wrote:
> Neil Bothwick <neil@digimed.co.uk> writes:
> > kde-base/kde is a meta package, it pulls in all the monolithic KDE
> > builds. If you are concerned about installation compile times, you should
> > not be trying to build the whole of KDE. Do you really need all of
> > kdegames, kdeedu and kdetoys to get your system running? Stick with
> > kde-base/kdebase or kde-base/kdebase-meta, you can cancel your current
> > emerge and merge one of these instead, then add the rest of what you want
> > once the system is running.
>
> I'm confused here. (even more..)
>
> Before starting the compile:
> I ran a comparision of `emerge -v -p kde' and
> emerge -v -p kde-meta
>
> The last showed a much larger pile of dependancies than the former.
> So I ran the former.
>
> I've now canceled as suggested and running `emerge kde-base/kdebase'
>
> It only showed the main kde-3.4X as dependancy. But with all the
> screwups I've managed to get these kde packages installed:
> (And don't need several of them)
>
> kde-base/kdegraphics-3.4.1-r1 *
> kde-base/kdelibs-3.4.1-r1 *
> kde-base/kdebase-pam-6 *
> kde-base/kde-env-3-r4 *
> kde-base/arts-3.4.1-r2 *
> kde-base/kdebase-3.4.1-r1 *
> kde-base/kdeartwork-3.4.1 *
> kde-base/kdepim-3.4.1-r2 *
> kde-base/kdegames-3.4.1 *
> kde-base/kdeutils-3.4.1 *
> kde-base/kdenetwork-3.4.1-r1 *
> kde-base/kdeedu-3.4.1-r1 *
--
Brett I. Holcomb
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-10 17:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 21:55 [gentoo-user] Is there and Alternative to compiling kde? Harry Putnam
2005-12-09 22:08 ` Jeff
2005-12-09 22:20 ` Tom Smith
2005-12-09 22:35 ` Gerhard Hoogterp
2005-12-09 22:50 ` Dale
2005-12-09 22:58 ` Tom Smith
2005-12-10 0:22 ` Neil Bothwick
2005-12-10 2:24 ` [gentoo-user] " Harry Putnam
2005-12-10 10:29 ` Neil Bothwick
2005-12-10 13:52 ` Harry Putnam
2005-12-10 1:39 ` Harry Putnam
2005-12-10 10:58 ` [gentoo-user] " Holly Bostick
2005-12-10 14:59 ` Gerhard Hoogterp
2005-12-10 15:44 ` Neil Bothwick
2005-12-09 23:02 ` Chris White
2005-12-10 0:42 ` Dale
2005-12-10 1:46 ` [gentoo-user] " Daniel da Veiga
2005-12-10 1:59 ` Harry Putnam
2005-12-14 3:07 ` Daevid Vincent
2005-12-14 6:14 ` Steven Susbauer
2005-12-14 6:20 ` Richard Fish
2005-12-14 20:42 ` Christoph Eckert
2005-12-14 9:43 ` Holly Bostick
2005-12-14 10:40 ` Neil Bothwick
2005-12-10 1:37 ` Harry Putnam
2005-12-10 1:47 ` Harry Putnam
2005-12-10 8:17 ` Chris White
2005-12-10 13:49 ` Harry Putnam
2005-12-10 15:49 ` Neil Bothwick
2005-12-10 16:31 ` Harry Putnam
2005-12-10 16:49 ` Brett I. Holcomb [this message]
2005-12-10 17:09 ` Neil Bothwick
2005-12-10 17:56 ` [gentoo-user] " Spider (D.m.D. Lj.)
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=200512101149.11364.brettholcomb@bellsouth.net \
--to=brettholcomb@bellsouth.net \
--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