emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34358: closed ([PATCH] gnu: python@2.7: Honor NIX_STORE.)


From: GNU bug Tracking System
Subject: bug#34358: closed ([PATCH] gnu: python@2.7: Honor NIX_STORE.)
Date: Mon, 27 Sep 2021 16:27:01 +0000

Your message dated Mon, 27 Sep 2021 18:25:54 +0200
with message-id <874ka6j88d.fsf@gnu.org>
and subject line Re: [bug#34358] [PATCH] gnu: python@2.7: Honor NIX_STORE.
has caused the debbugs.gnu.org bug report #34358,
regarding [PATCH] gnu: python@2.7: Honor NIX_STORE.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
34358: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34358
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] gnu: python@2.7: Honor NIX_STORE. Date: Wed, 06 Feb 2019 18:07:21 -0600 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Ludovic Courtès <ludo@gnu.org> writes:

> 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?

...

> Could you send an updated version of the patch?

Here it is!

> ./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.

"When creating the derivation" sounds like it's when the package is lowered
to a derivation, but from what I can see of ld-wrapper in (gnu packages
base) the actual substitution is done when the derivation is built. I
am curious how one would go about doing the substitution when the
package is lowered to a derivation, though. Anyway, for now I'm doing
the substitution at derivation-build-time.

> Last, the patch would need to go to ‘core-updates’ because of the number
> of rebuilds it entails.

Should I mention this somewhere?

Also, I should add that "guix lint" and indent-code.el both want changes
to gnu/packages/python.scm, but not due to changes I made. Should a
separate patch address those?

- reepca

Attachment: 0001-gnu-python-2.7-Honor-NIX_STORE.patch
Description: gnu: python@2.7: Honor NIX_STORE.


--- End Message ---
--- Begin Message --- Subject: Re: [bug#34358] [PATCH] gnu: python@2.7: Honor NIX_STORE. Date: Mon, 27 Sep 2021 18:25:54 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hi Sarah,

Sarah Morgensen <iskarian@mgsn.dev> skribis:

>>From 62e9e9a336ab5608405df8114f78c3cbb9dc3a39 Mon Sep 17 00:00:00 2001
>>From: Caleb Ristvedt <caleb.ristvedt@cune.org>
>>Date: Wed, 30 Jan 2019 17:00:32 -0600
>>Subject: [PATCH] gnu: python@2.7: Honor NIX_STORE.
>>
>>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.in: New file that causes
>>  python@2.7 to honor NIX_STORE at runtime or, if it isn't set, to use the
>>  NIX_STORE available when it was built.
>>
>>* gnu/packages/patches/python-2.7-site-prefixes.patch: Removed.
>>
>>* gnu/packages/python.scm (python-2.7): generates a patch from
>>  python-2.7-site-prefixes.patch.in at build-time and applies it.
>>  (python-3.7): don't apply that patch.
>>  (python2-minimal): inputs still need to include the patch utility and the
>>  patch.
>>
>>* gnu/local.mk: adjust patch name since it's been suffixed with ".in".
>
> Given that Python 2.7 is now EOL and Python 3 doesn't seem to use this
> NIX_STORE patch in the first place, is this patch still relevant?

Let’s close it and Caleb or anyone is welcome to reopen it if there’s
interest.

Thanks,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]