From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposed future EAPI feature: FILES whitelist
Date: Sat, 17 Sep 2016 06:42:58 +1200 [thread overview]
Message-ID: <20160917064258.76d91196@katipo2.lan> (raw)
In-Reply-To: <22492.15177.456611.482625@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Fri, 16 Sep 2016 20:34:49 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> That is, similar syntax as for SRC_URI? That would make parsing of the
> FILES variable by ebuilds practically impossible. So presumably, one
> would need another variable similar to A then, containing the files
> from FILES but without the USE-disabled ones.
Yeah, that's the sort of misgivings I had when I thought of a similar
idea myself.
I'd much rather a way to label groups of files by purpose, have portage
validate them, and then apply certain labels manually against certain
USE flags
For instance,
FILES["foo"] = "foo.patch bar.patch"
FILES["quux"] = "quux.patch"
...
if use foo; then
eapply $FILES["foo"]
else
eapply $FILES["quux"]
fi
But that gets into things that are too hard to do in bash, like named
arrays ( doable but unfamilar for most ) and arrays-in-named-arrays
( ummm )
Probably not a good idea to push the limitations of bash in this way.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-16 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 12:30 [gentoo-dev] Proposed future EAPI feature: FILES whitelist Kent Fredric
2016-09-16 15:20 ` Ulrich Mueller
2016-09-16 15:31 ` Mart Raudsepp
2016-09-16 16:00 ` Kent Fredric
2016-09-16 16:39 ` Zac Medico
2016-09-16 18:34 ` Ulrich Mueller
2016-09-16 18:42 ` Kent Fredric [this message]
2016-09-16 18:19 ` Ian Stakenvicius
2016-09-20 7:02 ` Michał Górny
2016-09-20 8:11 ` Kent Fredric
2016-09-20 16:14 ` Ulrich Mueller
2016-09-20 18:57 ` Kent Fredric
2016-09-20 19:05 ` Kent Fredric
2016-09-21 6:44 ` Ulrich Mueller
2016-09-21 10:03 ` Kent Fredric
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=20160917064258.76d91196@katipo2.lan \
--to=kentnl@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