From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why is KDE part of the system set?
Date: Thu, 24 Feb 2011 09:21:54 -0600 [thread overview]
Message-ID: <4D667792.6040805@gmail.com> (raw)
In-Reply-To: <20110224145551.2a749647@zaphod.digimed.co.uk>
Neil Bothwick wrote:
> On Thu, 24 Feb 2011 07:03:06 -0600, Dale wrote:
>
>
>> I just wonder if the devs have noticed how much this has grown when
>> packages with X flags are included in the system set?. Would Gnome do
>> the same? What about other GUI's?
>>
> What does it matter? They are only dependencies of @system, but they will
> also be dependencies of @world, because you have emerged kde-meta, so
> either way they would be on your system.
>
> There is nothing wrong with your system, it is doing exactly what you
> told it to with your USE flags, and the kde flag is not the culprit
> anyway as emerge -ep @system doesn't bring in any KDE stuff here.
>
>
I was always under the impression that @system was supposed to be a
limited set of packages to build, including dependencies. For me, if I
have a issue, I usually start with emerge -e system to see if it helps.
Since there is some KDE stuff in there, that makes it build packages
that I most likely don't need to be rebuilt. To me, KDE is not a system
package.
It is doing what it is told but it is also doing things that it didn't
use to do even when told the same as it is being told now. It wasn't to
long ago that system was about 150 packages and didn't take that long to
recompile. Now it is over 400. If this continues, the difference
between system and world is going to be small.
It may not be broke but it seems the system set is growing pretty quick.
Dale
:-) :-)
next prev parent reply other threads:[~2011-02-24 16:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 4:28 [gentoo-user] Why is KDE part of the system set? Dale
2011-02-23 9:29 ` Neil Bothwick
2011-02-23 11:47 ` Dale
2011-02-23 12:25 ` Neil Bothwick
2011-02-23 15:57 ` Dale
2011-02-23 22:52 ` Mike Edenfield
2011-02-24 0:16 ` Dale
2011-02-24 0:48 ` Alex Schuster
2011-02-24 11:40 ` Sebastian Beßler
2011-02-24 12:19 ` Dale
2011-02-24 2:08 ` Walter Dnes
2011-02-24 12:32 ` Dale
2011-02-24 12:47 ` Sebastian Beßler
2011-02-24 13:03 ` Dale
2011-02-24 13:23 ` Sebastian Beßler
2011-02-24 14:08 ` Dale
2011-02-24 14:55 ` Neil Bothwick
2011-02-24 15:21 ` Dale [this message]
2011-02-24 16:12 ` Neil Bothwick
2011-02-24 17:34 ` Dale
2011-02-24 19:35 ` Neil Bothwick
2011-02-25 1:08 ` Walter Dnes
2011-02-26 4:10 ` Dale
2011-02-26 13:54 ` Mark Knecht
2011-02-26 14:43 ` Neil Bothwick
2011-02-26 15:24 ` Dale
2011-02-26 15:46 ` Neil Bothwick
2011-02-26 21:59 ` Mike Gilbert
2011-02-24 17:32 ` Sebastian Beßler
2011-02-24 17:41 ` Mark Knecht
2011-02-24 17:52 ` Mark Knecht
2011-02-23 12:57 ` Joost Roeleveld
2011-02-23 14:31 ` Mark Knecht
[not found] <gpf97-vC-1@gated-at.bofh.it>
[not found] ` <gpjmq-7Ig-25@gated-at.bofh.it>
[not found] ` <gplxU-2ZI-5@gated-at.bofh.it>
[not found] ` <gpm0V-3W6-3@gated-at.bofh.it>
[not found] ` <gpprR-1yy-43@gated-at.bofh.it>
[not found] ` <gpyY9-15c-3@gated-at.bofh.it>
[not found] ` <gpIEa-Q1-3@gated-at.bofh.it>
[not found] ` <gpINP-141-13@gated-at.bofh.it>
[not found] ` <gpJ7d-1M3-31@gated-at.bofh.it>
2011-02-24 13:32 ` Elaine C. Sharpe
2011-02-24 14:18 ` Dale
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=4D667792.6040805@gmail.com \
--to=rdalek1967@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