From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] What is happening to the desktops?
Date: Sun, 28 Sep 2003 23:32:23 -0700 [thread overview]
Message-ID: <20030928233223.4b684269.cbrewer@stealthaccess.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
I was checking out the latest in the desktop area (I use a wm,and have for
a while, but I like to see what's new and exciting), and the amount of
depends getting listed is mind-boggling. For example, the KDE website says
there is very little (if any) dependencies..but if certain libs are found it
will build support for them..if not, you won't notice. For example-
divx4linux? portmap? fam? win32codecs? A lot of this stuff isn't triggered
by USE flags, either. I remember a ways back, emerging kde meant arts,qt and
the 13 or 15 kde packages..which strangely enough all started with kde*. I
rather suspect its the same in GNOME also, but it appears from a glance to a
much smaller extent. I realize that it's probably to add more function for
the busy or uninitiated, but after reading the previous threads, I too would
like to see things closer to vanilla. I remember the frustrations of doing
KDE from rpm and thinking stuff like "wtf, I don't want mysql or xanim or
xine or OBDC or any of this other crap, I want to see what it looks like
bare-bones style".
I know I'm prolly gonna hear the "if you don't like it, don't build it"
attitude at least once, but I'd just like to check something out without
building 30 pkgs I wont see just to check out the 15 I will.
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-29 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 6:32 C. Brewer [this message]
2003-09-29 6:45 ` [gentoo-dev] What is happening to the desktops? Norberto Bensa
2003-09-29 7:03 ` Mike Frysinger
2003-09-29 7:01 ` Mike Frysinger
2003-09-29 8:45 ` C. Brewer
2003-09-29 13:08 ` Caleb Tennis
2003-09-29 16:47 ` C. Brewer
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=20030928233223.4b684269.cbrewer@stealthaccess.net \
--to=cbrewer@stealthaccess.net \
--cc=gentoo-dev@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