From: Andrew Gaffney <agaffney@technaut.darktalker.net>
To: Gentoo Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] portage without portage
Date: Wed, 29 Oct 2003 11:46:14 -0600 [thread overview]
Message-ID: <3F9FFCE6.3010701@technaut.darktalker.net> (raw)
In-Reply-To: <20031029163753.GA5091@twobit.net>
Nick Jones wrote:
>>I think I'll just stick with what I know. For now, I'm just doing 'emerge
>>info | grep USE' to get a complete list of USE flags. As for the DEPEND
>>line, I'm using a regex to extract each item, although its not going too
>>well.
>
> You can't do it that way. Portage does a lot of calculations based on
> things like virtuals, inherited-values, and eclasses. USE flags also
> have the potential to change during dep calculation due to binary
> package restrictions and eventually USE requirements as well.
>
> The way you're getting USE is ok for single packages.
>
> The DEPEND info isn't right. DEPEND, RDEPEND, and PDEPEND all can vary
> inside of an eclass, and depending upon if they are unset, empty, or
> set, they can affect the final output.
I'm just going to pretend I didn't hear any of that :) Something I'm curious about: what
is the difference between the different *DEPEND lines?
--
Andrew Gaffney
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-10-29 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 7:32 [gentoo-dev] portage without portage Andrew Gaffney
2003-10-26 8:25 ` Kumba
2003-10-26 12:29 ` Bartosch Pixa
2003-10-27 16:16 ` Andrew Gaffney
2003-10-26 18:25 ` Kain
2003-10-29 16:37 ` Nick Jones
2003-10-29 17:46 ` Andrew Gaffney [this message]
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=3F9FFCE6.3010701@technaut.darktalker.net \
--to=agaffney@technaut.darktalker.net \
--cc=gentoo-dev@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