From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: {OT} Will ARM take over the world?
Date: Fri, 14 Dec 2012 12:13:11 -0500 [thread overview]
Message-ID: <20121214171311.GA5651@waltdnes.org> (raw)
In-Reply-To: <5360528.EJExW5v6pg@localhost>
On Thu, Dec 13, 2012 at 07:29:21PM +0100, Volker Armin Hemmann wrote
> SLAX is using KDE4 - and uses 200mb.
>
> KDE is flexible. If you have lots of memory, it does use lots of
> memory. If you don't it doesn't. So don't group it together with
> 'lets force mono unto our users - for a notes application' gnome or
> 'you can always add another 4gig' chrome.
What about 'lets force dbus/libmpeg2/qt-webkit/phonon and a relational
database on our users - for a pdf viewer'?
I have a stripped-down no-nonsense install on all my machines with the
USE variable beginning with "-*", and only necessary stuff being added.
When xpdf was deprecated, one of the suggested alternatives was
"okular". It requires qt3support, which in turn requires the
"accessibility" USE flag. And qt-gui is required which requires the
"dbus" flag. And oh yeah, I'd have to unmask dbus.
And dee first dependancy requires dee second dependancy
And dee second dependancy requires dee third dependancy
And dee third dependancy requires dee fourth dependancy
etc, etc, etc
After unmasking dbus and adding a bunch of USE flags, I finally got
rid of the emerge error messages...
USE="accessibility dbus glib qt3support sqlite gstreamer" emerge -p okular
Total: 59 packages (59 new), Size of downloads: 347,087 kB
A stinking pdf viewer requires, amongst other things...
libmpeg2 dbus desktop-file-utils strigi xdg-utils qt-webkit phonon
and *A RELATIONAL DATABASE* (Hello!?!?), of which the lightest available
is sqlite. Don't waste your time trying to convince me that KDE is
lightweight. I run ICEWM. See my sig...
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
prev parent reply other threads:[~2012-12-14 17:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 3:25 [gentoo-user] {OT} Will ARM take over the world? Grant
2012-12-09 3:51 ` Michael Mol
2012-12-09 19:24 ` Florian Philipp
2012-12-09 19:53 ` Marc Joliet
2012-12-11 2:00 ` Walter Dnes
2012-12-13 13:45 ` Walter Dnes
2012-12-09 3:52 ` microcai
2012-12-09 8:03 ` Alan McKinnon
2012-12-09 21:44 ` Grant
2012-12-10 5:49 ` Alan McKinnon
2012-12-09 23:23 ` Grant
2012-12-10 3:06 ` [gentoo-user] " James
2012-12-10 5:35 ` [gentoo-user] " Alan McKinnon
2012-12-10 15:46 ` [gentoo-user] " James
2012-12-10 18:18 ` [gentoo-user] " Volker Armin Hemmann
2012-12-10 19:06 ` [gentoo-user] " Grant Edwards
2012-12-10 19:15 ` Michael Mol
2012-12-10 19:33 ` Grant Edwards
2012-12-10 19:38 ` Alan McKinnon
2012-12-10 20:06 ` Grant Edwards
2012-12-10 20:20 ` Volker Armin Hemmann
2012-12-10 20:37 ` Alan McKinnon
2012-12-10 21:10 ` Grant
2012-12-10 21:23 ` Alan McKinnon
2012-12-10 21:33 ` Grant
2012-12-10 21:42 ` Alan McKinnon
2012-12-12 17:05 ` James
2012-12-12 17:26 ` Bruce Hill
2012-12-12 17:55 ` James
2012-12-12 18:40 ` Bruce Hill
2012-12-13 5:02 ` Alan McKinnon
2012-12-13 6:06 ` Pandu Poluan
2012-12-13 14:10 ` Bruce Hill
2012-12-13 0:33 ` Walter Dnes
2012-12-13 1:00 ` Grant
2012-12-13 11:24 ` Kevin Chadwick
2012-12-13 13:37 ` Walter Dnes
2012-12-13 18:29 ` Volker Armin Hemmann
2012-12-14 17:13 ` Walter Dnes [this message]
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=20121214171311.GA5651@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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