From: Ryan Tandy <tarpman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Simplified apache2
Date: Tue, 12 Sep 2006 16:27:34 -0700 [thread overview]
Message-ID: <45074266.7050301@gmail.com> (raw)
In-Reply-To: <558b73fb0609120808k799baf30j41560442b9c38d12@mail.gmail.com>
Michael Crute wrote:
> USE="-* hardened pic ncurses ssl crypt berkdb tcpd pam perl python
> readline"
Even this is a bit more bloated than it needs to be. I have never used
'tcpd' or 'berkdb' on any system I run, and 'perl' and 'python' are
*much* more useful (IMO) as local flags (in package.use) than as global
ones. Even 'ssl' doesn't *have* to be there, especially in the global
scope - 'www-client/links ssl' in package.use should be more than
sufficient. One flag missing from that line that I like to have is
'bzip2' - tar just isn't quite the same without bz2 support. ;)
Also, be careful using the hardened flag without running the hardened
profile. The hardened profile masks out a couple of packages and flags
that don't work so well on a hardened system.
BTW, the flags with underscores in them (kernel_linux, userland_GNU,
elibc_glibc, video_cards_radeon and such) are known as USE_EXPAND or
expanded USE flags. VIDEO_CARDS and ALSA_CARDS are a couple you may be
familiar with - when they're set in make.conf, emerge expands them
automatically, so e.g. VIDEO_CARDS="radeon" gets expanded to
USE="video_cards_radeon". KERNEL, USERLAND, and ELIBC are there for the
use of packages that work differently on different systems -
Gentoo/FreeBSD, Gentoo/OSX, and such - and should *only* be set by your
profile.
Hope I've helped. :)
Ryan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-12 23:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 13:40 [gentoo-user] Simplified apache2 James
2006-09-12 15:08 ` Michael Crute
2006-09-12 15:36 ` [gentoo-user] " James
2006-09-12 23:27 ` Ryan Tandy [this message]
2006-09-13 12:36 ` James
2006-09-13 13:20 ` Rumen Yotov
2006-09-14 17:05 ` Brian Davis
2006-09-14 21:49 ` Brian Davis
2006-09-13 13:50 ` Michael Crute
2006-09-13 17:01 ` Bo Ørsted Andresen
2006-09-13 17:52 ` Stefan G. Weichinger
2006-09-13 18:08 ` Neil Bothwick
2006-09-13 19:13 ` Daniel da Veiga
2006-09-13 21:11 ` Harm Geerts
2006-09-13 5:07 ` [gentoo-user] " Michael Stewart (vericgar)
2006-09-13 13:45 ` Michael Crute
2006-09-15 0:17 ` Michael Stewart (vericgar)
2006-09-13 18:17 ` Brian Davis
2006-09-14 2:41 ` [gentoo-user] " James
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 2:03 [gentoo-user] " bridavis
2006-09-14 2:16 ` Ryan Tandy
2006-09-14 2:43 bridavis
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=45074266.7050301@gmail.com \
--to=tarpman@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