1 |
Neil Bothwick wrote: |
2 |
> On Fri, 25 Feb 2011 22:10:27 -0600, Dale wrote: |
3 |
> |
4 |
> |
5 |
>> Not exactly. I'm saying I don't think X stuff should be in the system |
6 |
>> set regardless of USE flags. |
7 |
>> |
8 |
> There is no X stuff in @system. what you are seeing is that some |
9 |
> dependencies of @system have X in their IUSE, so pull in X, but that |
10 |
> doesn't make X part of @system, nor make it a requirement for your |
11 |
> computer to run. |
12 |
> |
13 |
> You have set the X flag, by choosing a desktop profile, so why do you |
14 |
> object to X programs being installed? |
15 |
> |
16 |
> |
17 |
|
18 |
I see your point but that isn't what I have been talking about. When I |
19 |
run emerge -e system, it pulls in a bunch of X stuff including KDE. |
20 |
Yea, it is because of USE flags but that didn't used to be the case. If |
21 |
I recall correctly, my system set and all its dependencies used to be |
22 |
147 packages. Now it is over 400 packages which includes things that |
23 |
have nothing to do with booting or running portage. |
24 |
|
25 |
I don't object to having X stuff installed, I just don't think it should |
26 |
be pulled into the system set. When I do a emerge -e system, it should |
27 |
be only stuff that is related to booting, running portage and such, not |
28 |
GUI stuff. |
29 |
|
30 |
If this continues to grow, the system set is going to catch up with the |
31 |
world set. |
32 |
|
33 |
Dale |
34 |
|
35 |
:-) :-) |