public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: warnera6@egr.msu.edu
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] use flags in both use.defaults and make.defaults
Date: Sun, 28 Aug 2005 15:46:05 -0400 (EDT)	[thread overview]
Message-ID: <1125258365.warnera6.squirrel@localhost> (raw)
In-Reply-To: <20050828193642.GA16550@linux1.home>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> since there has been a lot of discussion lately about default use flags,
> I looked at the profiles and found the following:
>
> All of these use flags are in base/use.defaults.  As I understand it, if
> the package listed with the flag in this file is installed on the
> system, the flag is automatically turned on.  If that's true, why are
> they also listed in default-linux/x86/make.defaults?  Wouldn't it be
Obviously because default-linux/x86 is the only profile worth looking at :)
Try looking at the default use flags for say, the s390 profile :)

I still agree with your point "stuff in both places" but I think it's more
of an "it's there because it doesn't work right otherwise" rather than
some sort of USE flag conspiracy ;)

> better to have them turned on automatically when the package that
> installs them is merged?
>
> arts cups eds emboss foomaticdb gnome kde nls opengl perl python tcpd X
>
> I also found the following flags in both places.  The difference here is
> that the packages listed with these in base/use.defaults are libraries.
> Again, do these need to be listed in both places?  I would think these
> don't need to be in base/use.defaults if we are going to allow the user
> to turn on/off support for them.
>
> alsa berkdb gdbm gif gpm gstreamer gtk imlib libwww mad mikmod motif
> ncurses ogg pam pdflib png qt readline sdl ssl vorbis zlib
>
> any thoughts?

I believe in the current implementation of use.defaults the use flag is
not propagated backwards through the buildplan.  So you "USE="-everything
in /etc/make.profile/make.defaults" emerge xmms alsa" and xmms won't have
the ALSA use flag set, because alsa was merged second.  I'd have to double
check with Jason or Brian though..haven't talked about implentation of
use.defaults in a while *pokes*.

> William
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDEhJKblQW9DDEZTgRAlzaAKCc+sLiwCO6HCE+UUnOvrnhY7f4kwCgoqkx
> Xzz8eV610fWxhZ6ccQ+adZ4=
> =HC0T
> -----END PGP SIGNATURE-----
> --
> gentoo-dev@gentoo.org mailing list
>


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-08-28 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 19:36 [gentoo-dev] use flags in both use.defaults and make.defaults William Hubbs
2005-08-28 19:46 ` warnera6 [this message]
2005-08-28 19:46 ` Mike Frysinger

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=1125258365.warnera6.squirrel@localhost \
    --to=warnera6@egr.msu.edu \
    --cc=gentoo-dev@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