From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] USE variables in SRC_URI
Date: Tue Oct 2 13:01:02 2001 [thread overview]
Message-ID: <200110021900.VAA21902@mailgw3.netvision.net.il> (raw)
In-Reply-To: <20011002123929.E25316@cvs.gentoo.org>
> You actually can't do it that way, because it will cause incomplete digests
> to be generated if "foo" isn't set in USE. The new system auto-adjusts so
> that maintainers always generate correct digests, but normal users only
> need to download the files they need.
As I understand this, you download everything if MAINTAINER is set. Then, I
suppose, you also get a ${A} with all the files you downloaded and you unpack
them all.
Normally this isn't a problem, but in theory: an ebuild might use ${A} to do
some "for x in" etc. processing to avoid putting use flag tests in both
SRC_URI and every function. (Together with DEPEND and RDEPEND there are 5
places where you typically query use flags, plus the 4 pkg_ functions.) This
is a very rare case, but after working with eclasses I'm used to thinking in
a generic way about these things.
So: I propose that to make ebuilds behave the same way regardless of
MAINTAINER, we should set $A the proper way, and download all files anyway.
Perhaps you think this issue isn't very important; I admit I never wrote or
saw an ebuild that behaved like this. But they might.
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-10-02 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 0:41 [gentoo-dev] USE variables in SRC_URI Daniel Robbins
2001-10-02 2:23 ` Mikael Hallendal
2001-10-02 12:36 ` Morgan Christiansson
2001-10-02 12:40 ` Daniel Robbins
2001-10-02 13:01 ` Dan Armak [this message]
2001-10-02 13:05 ` Daniel Robbins
2001-10-02 13:07 ` Mikael Hallendal
2001-10-02 13:10 ` Dan Armak
2001-10-02 14:17 ` Mikael Hallendal
2001-10-02 14:17 ` Mikael Hallendal
2001-10-02 14:21 ` Dan Armak
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=200110021900.VAA21902@mailgw3.netvision.net.il \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.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