From: Pieter Van den Abeele <pvdabeel@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Pieter Van den Abeele <pvdabeel@gentoo.org>
Subject: Re: [gentoo-portage-dev] /etc/make.profile/use.defaults
Date: Wed, 12 May 2004 17:43:41 +0200 [thread overview]
Message-ID: <24B267F2-A42B-11D8-9922-0003938E7E46@gentoo.org> (raw)
In-Reply-To: <40A2409A.5000000@skylineaero.com>
On 12 May 2004, at 17:19, Andrew Gaffney wrote:
>> I've come across another issue. 'emerge -epvt xfree' shows that
>> python wants to install tcl and tk because of the 'tcltk' USE flag
>> where my program doesn't. That USE flag is not defined in my
>> /etc/make.profile/make.defaults or /etc/make.conf. 'ufed' shows that
>> it is defined in /etc/make.profile/use.defaults. I've never come
>> across this file before. What does it do?
>
> Nevermind. From 'man portage':
>
> use.defaults
> Here we DO NOT define the default USE flags, but the
> so-called
> auto-USE flags. This rather unknown portage feature activates a
> USE
> flag if a specific package is installed and the flag was not
> explicitly
> deactivated. This file contains the associations between USE
> flags and
> packages that trigger the auto-USE feature.
>
> In other words, if we never put "sdl" or "-sdl" into our USE, but
> we have
> media-libs/libsdl emerged, then portage automagically sticks "sdl"
> into our
> USE for us.
>
> Format:
> - comments begin with #
> - one USE flag per line with a list of DEPEND atom bases
>
> Example:
> # media-libs/libsdl will activate "sdl"
> sdl media-libs/libsdl
> # activate tcltk only if we have both
> # dev-lang/tcl and dev-lang/tk
> tcltk dev-lang/tcl dev-lang/tk
>
> That makes sense, but shouldn't Portage not use these when operating
> with the '--emptytree' flag since it pretends that nothing is
> installed?
I think that with 'installed' in this case they also include 'scheduled
for installation' (although I'm not 100% sure). For instance If portage
schedules tcl and tk in an emptytree, then the tcltk useflag will be
enabled for packages having IUSE="tcltk" that are added to the schedule
afterwards.
Pieter
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-05-12 15:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 3:02 [gentoo-portage-dev] building dependency tree Andrew Gaffney
2004-05-12 5:14 ` Pieter Van den Abeele
2004-05-12 6:42 ` Andrew Gaffney
2004-05-12 7:59 ` Pieter Van den Abeele
2004-05-12 14:43 ` Andrew Gaffney
2004-05-12 15:02 ` Pieter Van den Abeele
2004-05-12 15:14 ` [gentoo-portage-dev] /etc/make.profile/use.defaults (was: building dependency tree) Andrew Gaffney
2004-05-12 15:19 ` [gentoo-portage-dev] /etc/make.profile/use.defaults Andrew Gaffney
2004-05-12 15:43 ` Pieter Van den Abeele [this message]
2004-05-12 15:44 ` Andrew Gaffney
2004-05-12 16:03 ` Pieter Van den Abeele
2004-05-12 16:08 ` Andrew Gaffney
2004-05-12 16:33 ` Jason Stubbs
2004-05-12 16:39 ` Andrew Gaffney
2004-05-12 17:28 ` Jason Stubbs
2004-05-12 16:25 ` [gentoo-portage-dev] building dependency tree Jason Stubbs
2004-05-15 4:12 ` Andrew Gaffney
2004-05-15 6:14 ` Jason Stubbs
2004-05-15 6:50 ` Andrew Gaffney
2004-05-15 7:06 ` Jason Stubbs
2004-05-15 15:31 ` Andrew Gaffney
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=24B267F2-A42B-11D8-9922-0003938E7E46@gentoo.org \
--to=pvdabeel@gentoo.org \
--cc=gentoo-portage-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