public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Riyad Kalla <rsk@u.arizona.edu>
Cc: "'M. Zuelsdorff'" <micha@dolbyco.de>, Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] mplayer with dvdread -- use flag comment
Date: 10 Apr 2003 23:15:50 +0200	[thread overview]
Message-ID: <1050009350.20070.22.camel@nosferatu.lan> (raw)
In-Reply-To: <003901c2ffa1$e5d38f60$d628c480@rskwork>

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

On Thu, 2003-04-10 at 22:43, Riyad Kalla wrote:
> I'm starting to feel more like this, WGT the use flags... when I
> installed gentoo on a server here at work, I left the use flags alone,
> figuring "hey it's a server" but then I noticed that certain packages
> WANTED to install some rediculous amounts of optional requirements, so I
> started using "-" use flags, and that seemed to work. Then I noticed
> other packages building without supports for things I needed (like
> CUPS). Anywya, after compiling and recompiling KDE about 3 times, mysql
> twice, qt 3 times and a few utilities I started to think that before
> installing a program, I'd rather just see the "configure --help" options
> and decide what I wanted and what I didn't... this use flag business is
> kinda trickie... I couldn't imagine trying to code to take it all into
> account. Has there ever been talk to get rid of use flags and tackle
> optional package params in a different way?
> 

The logical would have been:

  - I want a server, so no X, sound, KDE, Gnome, etc, so add
    to USE: -X -gnome -kde -xv -alsa -oss -esd -avi -mikmod -mpeg
            -oggvorbis -opengl -qt -quicktime -sdl -spell -svga
            -truetype -xmms
  - It will be samba print server, so we need cups, so add: cups
  - etc

So USE will be:

USE="-X -gnome -kde -xv -alsa -oss -esd -avi -mikmod -mpeg -oggvorbis
-opengl -qt -quicktime -sdl -spell -svga -truetype -xmms"

No cups is needed, as its already in the default USE flags.  What
those are, look at:

  /etc/make.profile/make.defaults

Note that you should not edit this file by hand.

  
Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-10 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 22:48 [gentoo-dev] mplayer with dvdread M. Zuelsdorff
2003-04-09 21:47 ` Martin Schlemmer
2003-04-10  8:38   ` Henti Smith
2003-04-10 17:49     ` Martin Schlemmer
2003-04-10 21:32   ` M. Zuelsdorff
2003-04-10 20:43     ` [gentoo-dev] mplayer with dvdread -- use flag comment Riyad Kalla
2003-04-10 21:15       ` Martin Schlemmer [this message]
2003-04-10 21:25         ` Riyad Kalla
2003-04-10 21:55           ` Martin Schlemmer
2003-04-10 21:02     ` [gentoo-dev] mplayer with dvdread Martin Schlemmer
2003-04-10 21:22       ` Riyad Kalla
2003-04-10 21:52         ` Martin Schlemmer
2003-04-10 21:54     ` Fred Van Andel
2003-04-11 19:55       ` Fred Van Andel
2003-04-11 18:09     ` Thilo Bangert

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=1050009350.20070.22.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=micha@dolbyco.de \
    --cc=rsk@u.arizona.edu \
    /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