Walter Dnes wrote:
On Thu, Feb 24, 2011 at 11:34:09AM -0600, Dale wrote
I didn't tell portage to include KDE, qt, and a boatload of other stuff
to be part of @system. Did I enable the kde USE flag, yea. That should
be part of the world stuff not the system stuff. If I disable kde, qt
and all the others then my GUI is going to be junk if it would even work
at all.
What you're saying is that you want *SOME*, but not all, packages to
be built with certain flags. That's what package.use was designed for.
If you enable "kde" globally in your USE var, everything that can be
built with KDE support will be built with KDE support. If you enable it
for only certain packages, it will only show up for certain packages.
Not exactly. I'm saying I don't think X stuff should be in the system
set regardless of USE flags. Not to long ago, there was only a 150 or
so packages for system regardless of the USE flags. That has changed.
I have had KDE installed on this system since day one as well as on my
old system. Only recently has KDE and other X stuff been pulled into
the system set.
You have "kde" and "symantic-desktop" in your USE, sorry, you're going
to pull in a lot of crap, no if's-and's-or's-but's. BTW, I assure you
that I am absolutely neutral in the GNOME/KDE war... the pox on both
their houses. I didn't buy a computer to run desktops, I bought a
computer to run applications.
True, it does pull in a lot. That shouldn't be in the system set tho.
It wasn't in the past and it shouldn't be now either.
Now it's possible that many of the flags in your "combined" USE are
pulled in by your profile. The way to avoid that is to start your USE
with "-*" and only add what is absolutely necessary, either in USE in
make.conf or on a package-by-package basis in package.use. I started
doing that some years ago after the developers "in their infinite
wisdom" decided to include "ipv6" by default. Firefox and mplayer and
anything else that connected to the net would spin their wheels for 30
to 45 seconds, while IPV6 DNS requests timed out, and then fall back to
IPV4. I did *NOT* appreciate that.
If I am going to put "-*" in my make.conf, I may as well not select any
profile except for the base profile. After all, that disables
everything that the kde profile enables. Since I use KDE about 99.99%
of the time, I may as well use that profile. ;-)
I rarely put anything in package.use. As you can tell by my USE line,
it's hard enough keeping up with config files already. It's more than
enough fun trying to keep up with package.mask. You know, you add a
package to package.unmask but forgot it is in package.mask and can't
figure out why it is still masked. A person could go in circles for a
while before thinking about it being masked locally instead of by a dev
in the tree. lol I'm pleading the 5th on the number of times that has
happened too. My lips are sealed. :-|
I guess the kernel will have the kde USE flag next. lol At least
that should be in @system tho. ;-)
Check your profile. Is it kde-desktop? And while you're at it, set
your "ALSA_CARDS" variable in /etc/make.conf. It seems to be pulling in
everything by default.
I thought the ALSA_CARDS was set but it was commented out. I guess I
put it in but forgot to remove the # so that it would see the setting.
I guess my sound would have worked regardless of what sound card I had.
lol
To make my point, in the past couple days I was having random reboots.
I booted from a USB stick, mounted my partitions and wanted to do a
QUICK emerge -e system. Here I go compiling KDE stuff that works and
doesn't need to be recompiled. I'm not to concerned about KDE, I'm just
wanting to recompile the root of my system, the system packages and a
new kernel. I didn't need KDE pulled into the mix.
Dale
:-) :-)
