From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: 27003@debbugs.gnu.org
Subject: bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python.
Date: Sat, 20 May 2017 11:37:42 +0200 [thread overview]
Message-ID: <20170520093742.2115-1-alex@pompo.co> (raw)
Hello,
This patch series goes back some time, but the need for it has not
disappeared.
It implements a general `wrap` phase that can be used in individual build
systems to make sure binaries in those languages have access to all their
propagated inputs at runtime, by setting an appropriate environment variable.
I tested it against perl and python packages.
It will need to go in core-updates due to the number of packages that will
need to be rebuilt.
Best wishes,
Alex
Alex Sassmannshausen (3):
build/utils: Add 'program-wrapper'.
build/perl-build-system: Add 'wrap' phase.
build/python-build-system: Refactor 'wrap'.
guix/build/perl-build-system.scm | 15 +++++++++++++--
guix/build/python-build-system.scm | 36 ++++++++----------------------------
guix/build/utils.scm | 36 ++++++++++++++++++++++++++++++++++++
3 files changed, 57 insertions(+), 30 deletions(-)
--
2.12.2
next reply other threads:[~2017-05-20 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 9:37 Alex Sassmannshausen [this message]
2017-05-20 9:40 ` bug#27003: [PATCH 1/3] build/utils: Add 'program-wrapper' Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 2/3] build/perl-build-system: Add 'wrap' phase Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 3/3] build/python-build-system: Refactor 'wrap' Alex Sassmannshausen
2017-05-20 20:23 ` bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python Marius Bakke
2017-05-27 19:04 ` Arun Isaac
2017-05-28 19:08 ` Arun Isaac
2017-05-29 13:45 ` Alex Sassmannshausen
2017-05-30 13:45 ` Arun Isaac
[not found] ` <ef869600.AEMAK2iO_jkAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLXea@mailjet.com>
2017-05-30 15:17 ` Marius Bakke
2020-03-21 14:23 ` Brice Waegeneire
2020-03-21 16:32 ` 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=20170520093742.2115-1-alex@pompo.co \
--to=alex.sassmannshausen@gmail.com \
--cc=27003@debbugs.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).