From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Simplified apache2
Date: Tue, 12 Sep 2006 13:40:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20060912T142340-527@post.gmane.org> (raw)
Hello,
I used 2006.1 livecd to install a pII machine. It's going
to becomme a (minimalistic) apache2 server. I just let the
installation
set the flags for the install so I have these flags currently:
CURRENT
USE=" X alsa arts avi berkdb bitmap-fonts cairo cdr cli crypt
cups dbus dlloader
dri dvd dvdr eds elibc_glibc emboss encode esd fam firefox
fortran gdbm gif
gnome gpm gstreamer gtk hal input_devices_evdev
input_devices_keyboard
input_devices_mouse ipv6 isdnlog jpeg kde kernel_linux
ldap libg++ mad mikmod
mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre
pdflib perl png ppds
pppd python qt3 qt4 quicktime readline reflection sdl session
spell spl ssl tcpd
truetype truetype-fonts type1-fonts udev unicode
userland_GNU vorbis win32codecs
x86 xml xorg xv zlib apache2 "
Some of these flag look questionable, such as the one with
underscores (kernel_linux userland_GNU) as I only found
information on them, where they are describe as 'undocumented
use flags'. What's up with these flags?
Where do I look to discern the minimal list of (necessary) system
flags that
must be kept? (I want to avoid negating any flags that are critical).
These are my proposed list of flags:
PROPOSED
USE=" berkdb bitmap-fonts dbus hal jpeg ldap mp3 mpeg ncurses
nls nptl nptlonly
ogg pam pcre pdflib perl png python quicktime readline sdl ssl
tcpd truetype
truetype-fonts type1-fonts udev unicode vorbis win32codecs xml
xv zlib apache2 "
So can I just use this list, or do I have to incluce a -{flag} for each one?
IS there simmpler syntax to globally remove unwanted flags [-*], but, not any
critical system flags? (Is this the same as just leaving the flag out
of the USE param. setting in make.conf?
Are there default system flag settings that I can safely remove?
Where is the list and how do I know which ones can be removed or negated?
My (limited) understanding of flags are that the highest priority are
those set in /etc/portage/package.use, then /etc/make.conf then
the system default flags which may be located in several locations.
Is there any docs or listing of all of these location and details
on precedence?
James
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-09-12 13:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 13:40 James [this message]
2006-09-12 15:08 ` [gentoo-user] Simplified apache2 Michael Crute
2006-09-12 15:36 ` [gentoo-user] " James
2006-09-12 23:27 ` [gentoo-user] " Ryan Tandy
2006-09-13 12:36 ` [gentoo-user] " 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=loom.20060912T142340-527@post.gmane.org \
--to=wireless@tampabay.rr.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