public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_nofetch: $A vs. $SRC_URI
Date: Wed, 05 Jul 2006 20:48:52 +0300	[thread overview]
Message-ID: <44ABFB84.3000902@gentoo.org> (raw)
In-Reply-To: <44AC00A0.6080702@gentoo.org>

Zac Medico schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Marius Mauch wrote:
>> Zac Medico schrieb:
>>> If a version of SRC_URI that has all the conditionals evaluated is
>>> needed in the ebuild environment, then I think we should use a new
>>> variable name.  Otherwise, it's ambiguous.
>> Doesn't $AA already satisfy the requirements?
> 
> Well, I think AA only contains file names, rather than the full URIs.  So, that's not quite the same as SRC_URI with all of it's conditionals evaluated.

It's the same as $A, just for all entries instead of "enabled" entries.
So for URIs we'd need two new variables.
Thinking about it it might be more useful to provide two generic bash 
functions to parse and evaluate DEPEND-like strings in portageq for 
example instead of special casing SRC_URI here.

Marius
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-07-05 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  1:00 [gentoo-dev] pkg_nofetch: $A vs. $SRC_URI Robin H. Johnson
2006-07-04  2:13 ` Donnie Berkholz
2006-07-04  2:36   ` Robin H. Johnson
2006-07-04 18:59     ` Donnie Berkholz
2006-07-04 19:35     ` Zac Medico
2006-07-04 20:08       ` Robin H. Johnson
2006-07-05  9:29       ` Marius Mauch
2006-07-05 18:10         ` Zac Medico
2006-07-05 17:48           ` Marius Mauch [this message]
2006-07-04 18:45 ` Mike Frysinger
2006-07-04 19:32   ` Mike Frysinger
2006-07-04 20:10     ` Robin H. Johnson
2006-07-04 20:56       ` 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=44ABFB84.3000902@gentoo.org \
    --to=genone@gentoo.org \
    --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