From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org, Caleb Ristvedt <caleb.ristvedt@cune.org>
Subject: Re: 01/09: patches: honor NIX_STORE in site.py.
Date: Tue, 05 Feb 2019 00:14:01 +0100 [thread overview]
Message-ID: <87y36vjgee.fsf@gnu.org> (raw)
In-Reply-To: <20190204192243.A58BA20B45@vcs0.savannah.gnu.org> (guix-commits's message of "Mon, 4 Feb 2019 14:22:43 -0500 (EST)")
Hello reepca,
Since you mentioned on IRC that this commit is a candidate for ‘master’,
I’m replying here.
Perhaps in the future you could email guix-patches@gnu.org for specific
commits like this one, especially when it’s not strictly related to the
daemon?
guix-commits@gnu.org skribis:
> commit c44484dc2008f624788a228925e6cef2bdc6c917
> Author: Caleb Ristvedt <caleb.ristvedt@cune.org>
> Date: Wed Jan 30 17:00:32 2019 -0600
>
> patches: honor NIX_STORE in site.py.
>
> Previously various python packages would fail to work unless the store they
> were kept in was /gnu/store. This fixes that.
>
> * gnu/packages/patches/python-2.7-site-prefixes.patch: Try NIX_STORE first
> and only use /gnu/store as a fallback.
[...]
> --- a/configure.ac
> +++ b/configure.ac
> @@ -295,7 +295,8 @@ AC_CONFIG_FILES([Makefile
> po/guix/Makefile.in
> po/packages/Makefile.in
> etc/guix-daemon.cil
> - guix/config.scm])
> + guix/config.scm
> + gnu/packages/patches/python-2.7-site-prefixes.patch])
./configure does not generate any patch files based on patch templates,
and that’s on purpose. Instead, when we need something like this, we
handle it the way ld-wrapper.in is handled: by doing the substitution
when creating the derivation.
In this case I’d suggest substituting @storedir@ in a post-unpack phase.
Does that make sense?
Also, the summary line of the commit message should be something like:
gnu: python@2.7: Honor NIX_STORE.
Last, the patch would need to go to ‘core-updates’ because of the number
of rebuilds it entails.
Could you send an updated version of the patch?
Thanks,
Ludo’.
next parent reply other threads:[~2019-02-04 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190204192241.15758.66035@vcs0.savannah.gnu.org>
[not found] ` <20190204192243.A58BA20B45@vcs0.savannah.gnu.org>
2019-02-04 23:14 ` Ludovic Courtès [this message]
2019-02-07 0:07 ` [bug#34358] [PATCH] gnu: python@2.7: Honor NIX_STORE Caleb Ristvedt
2021-09-26 2:31 ` Sarah Morgensen
2021-09-27 16:25 ` bug#34358: " Ludovic Courtès
[not found] ` <20190204192243.D1BD820B84@vcs0.savannah.gnu.org>
2019-02-09 22:09 ` 02/09: guix: store: Make register-items transactional, register drv outputs Ludovic Courtès
2019-02-13 8:43 ` Caleb Ristvedt
2019-03-06 13:14 ` Ludovic Courtès
2019-04-01 17:53 ` Caleb Ristvedt
2019-04-01 19:43 ` Ludovic Courtès
2019-04-04 16:20 ` Ludovic Courtès
2019-04-06 23:57 ` Caleb Ristvedt
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=87y36vjgee.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=caleb.ristvedt@cune.org \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.