From: Maxime Devos <maximedevos@telenet.be>
To: Marius Bakke <marius@gnu.org>, 57717@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#57717] [DRAFT PATCH core-updates] build-systems: Pass #:allowed-references and #:disallowed-references to builders.
Date: Sat, 10 Sep 2022 18:27:03 +0200 [thread overview]
Message-ID: <b08daa5d-0726-4a90-2fb1-c96eec1f130b@telenet.be> (raw)
In-Reply-To: <20220910152604.3459-1-marius@gnu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1363 bytes --]
On 10-09-2022 17:26, Marius Bakke wrote:
> This way we don't have to build the list of disallowed references twice,
> which is difficult without labels in the case of e.g. `(,glib "bin").
>
> Note: I implemented a variant of this approach using a let-binding in
> f0114656876dcf2e09874e4ea0c00cacf31f1bb2, perhaps that is "good enough"
> as this approach is unlikely to be much used.
>
> WDYT? I'll implement this for the remaining build systems if this is at
> all sane.
A caveat with using #:disallowed-references this way -- AFAIK, it is
undocumented whether #:disallowed-references goes for a native build or
a cross-build. The intention is to stop the (natively-)compiled
python-some-testing-library from appearing in the wrappers, stopping a
cross-compiled python-some-testing-library.
Depending on what, exactly, the behaviour of #:disallowed-references is,
it may be necessary to ‘override’ whether to disallow the native- or the
cross-version.
To do so, I used 'gexp-input' with #:native? #true in (gnu packages
glib) (maybe that was unnecessary, but I was thinking better be explicit
than implicit here ...).
An alternative solution could be to split #:disallowed-reference in two,
e.g. #:disallowed-references/system and #:disallowed-references/target,
to prevent accidents.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-10 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 15:26 [bug#57717] [DRAFT PATCH core-updates] build-systems: Pass #:allowed-references and #:disallowed-references to builders Marius Bakke
2022-09-10 16:27 ` Maxime Devos [this message]
2022-09-10 16:32 ` Maxime Devos
2022-09-10 16:34 ` Maxime Devos
2022-09-11 14:12 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b08daa5d-0726-4a90-2fb1-c96eec1f130b@telenet.be \
--to=maximedevos@telenet.be \
--cc=57717@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=marius@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).