* What to do when a package is removed upstream
@ 2021-04-20 8:24 Bonface Munyoki K.
2021-04-20 8:35 ` Tobias Geerinckx-Rice
0 siblings, 1 reply; 6+ messages in thread
From: Bonface Munyoki K. @ 2021-04-20 8:24 UTC (permalink / raw)
To: help-guix; +Cc: Pjotr Prins
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Hi Guix!
What do you do when you want to use a package that
has already been removed from guix. An example is
that I have a legacy project that I help maintain
that still uses some old python2 packages. One of
them is python2-flask*. Right now, as a work
around, I manually write the package definitions
somewhere and build those; but I feel there are
better ways of doing that. What ways, if any, are
those?
* Removed in bce0165f7c818a2c2764ee1a12e1b3a4b642e0ad
--
Bonface M. K. D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
Free Software Activist
Humble GNU Emacs User / Bearer of scheme-y parens
Curator: <https://upbookclub.com> / Twitter: @BonfaceKilz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What to do when a package is removed upstream
2021-04-20 8:24 What to do when a package is removed upstream Bonface Munyoki K.
@ 2021-04-20 8:35 ` Tobias Geerinckx-Rice
2021-04-20 16:24 ` Leo Famulari
2021-04-23 9:53 ` Bonface Munyoki K.
0 siblings, 2 replies; 6+ messages in thread
From: Tobias Geerinckx-Rice @ 2021-04-20 8:35 UTC (permalink / raw)
To: Bonface Munyoki K.; +Cc: Pjotr Prins, help-guix
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Bonface,
Bonface Munyoki K. writes:
> What do you do when you want to use a package that
> has already been removed from guix. An example is
> that I have a legacy project that I help maintain
> that still uses some old python2 packages. One of
> them is python2-flask*. Right now, as a work
> around, I manually write the package definitions
> somewhere and build those; but I feel there are
> better ways of doing that. What ways, if any, are
> those?
You can use an ‘inferior’[0] Guix if you don't mind the entire
closure of python2-flask* being frozen in the past -- possibly
including incompatibilities or known security vulnerabilities.
I don't know what their inclusion & maintenance criteria are, but
another approach is to add the removed packages to the
guix-past[1] channel.
Kind regards,
T G-R
[0]: https://guix.gnu.org/manual/devel/en/html_node/Inferiors.html
[1]: https://gitlab.inria.fr/guix-hpc/guix-past
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What to do when a package is removed upstream
2021-04-20 8:35 ` Tobias Geerinckx-Rice
@ 2021-04-20 16:24 ` Leo Famulari
2021-04-23 9:53 ` Bonface Munyoki K.
1 sibling, 0 replies; 6+ messages in thread
From: Leo Famulari @ 2021-04-20 16:24 UTC (permalink / raw)
To: Tobias Geerinckx-Rice; +Cc: Bonface Munyoki K., help-guix, Pjotr Prins
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On Tue, Apr 20, 2021 at 10:35:10AM +0200, Tobias Geerinckx-Rice wrote:
> You can use an ‘inferior’[0] Guix if you don't mind the entire closure of
> python2-flask* being frozen in the past -- possibly including
> incompatibilities or known security vulnerabilities.
>
> I don't know what their inclusion & maintenance criteria are, but another
> approach is to add the removed packages to the guix-past[1] channel.
It might be nice to document these options somehow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What to do when a package is removed upstream
2021-04-20 8:35 ` Tobias Geerinckx-Rice
2021-04-20 16:24 ` Leo Famulari
@ 2021-04-23 9:53 ` Bonface Munyoki K.
2021-04-23 12:06 ` Ricardo Wurmus
1 sibling, 1 reply; 6+ messages in thread
From: Bonface Munyoki K. @ 2021-04-23 9:53 UTC (permalink / raw)
To: Tobias Geerinckx-Rice; +Cc: help-guix, Pjotr Prins
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
Hi Tobias!
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Bonface,
>
> Bonface Munyoki K. writes:
>> What do you do when you want to use a package that
>> has already been removed from guix. An example is
>> that I have a legacy project that I help maintain
>> that still uses some old python2 packages. One of
>> them is python2-flask*. Right now, as a work
>> around, I manually write the package definitions
>> somewhere and build those; but I feel there are
>> better ways of doing that. What ways, if any, are
>> those?
>
> You can use an ‘inferior’[0] Guix if you don't
> mind the entire closure of python2-flask* being
> frozen in the past -- possibly including
> incompatibilities or known security
> vulnerabilities.
>
> I don't know what their inclusion & maintenance
> criteria are, but another approach is to add the
> removed packages to the guix-past[1] channel.
>
I reckon using guix-past (or another channel)
would be the way to go. I can't see any packages
that use "inferiors" yet; when that happens, it'd
be a good idea to start considering it!
> Kind regards,
>
> T G-R
>
> [0]: https://guix.gnu.org/manual/devel/en/html_node/Inferiors.html
> [1]: https://gitlab.inria.fr/guix-hpc/guix-past
>
--
Bonface M. K. D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
Free Software Activist
Humble GNU Emacs User / Bearer of scheme-y parens
Curator: <https://upbookclub.com> / Twitter: @BonfaceKilz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What to do when a package is removed upstream
2021-04-23 9:53 ` Bonface Munyoki K.
@ 2021-04-23 12:06 ` Ricardo Wurmus
2021-04-23 13:26 ` Bonface Munyoki K.
0 siblings, 1 reply; 6+ messages in thread
From: Ricardo Wurmus @ 2021-04-23 12:06 UTC (permalink / raw)
To: Bonface Munyoki K.; +Cc: help-guix, Pjotr Prins
Bonface Munyoki K. <me@bonfacemunyoki.com> writes:
>> You can use an ‘inferior’[0] Guix if you don't
>> mind the entire closure of python2-flask* being
>> frozen in the past -- possibly including
>> incompatibilities or known security
>> vulnerabilities.
>>
>> I don't know what their inclusion & maintenance
>> criteria are, but another approach is to add the
>> removed packages to the guix-past[1] channel.
>>
> I reckon using guix-past (or another channel)
> would be the way to go. I can't see any packages
> that use "inferiors" yet; when that happens, it'd
> be a good idea to start considering it!
To clarify: no packages distributed in the official Guix channel
itself will ever use an inferior. Inferiors can, however, be used
effectively in user manifests to install packages from the past
(or using a particular combination of channels).
--
Ricardo
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What to do when a package is removed upstream
2021-04-23 12:06 ` Ricardo Wurmus
@ 2021-04-23 13:26 ` Bonface Munyoki K.
0 siblings, 0 replies; 6+ messages in thread
From: Bonface Munyoki K. @ 2021-04-23 13:26 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: help-guix, Pjotr Prins
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Bonface Munyoki K. <me@bonfacemunyoki.com> writes:
>
>>> You can use an ‘inferior’[0] Guix if you don't
>>> mind the entire closure of python2-flask* being
>>> frozen in the past -- possibly including
>>> incompatibilities or known security
>>> vulnerabilities.
>>>
>>> I don't know what their inclusion & maintenance
>>> criteria are, but another approach is to add the
>>> removed packages to the guix-past[1] channel.
>>>
>> I reckon using guix-past (or another channel)
>> would be the way to go. I can't see any packages
>> that use "inferiors" yet; when that happens, it'd
>> be a good idea to start considering it!
>
> To clarify: no packages distributed in the
> official Guix channel itself will ever use an
> inferior. Inferiors can, however, be used
> effectively in user manifests to install packages
> from the past (or using a particular combination
> of channels).
I see. Thanks for the clarification.
--
Bonface M. K. D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
Free Software Activist
Humble GNU Emacs User / Bearer of scheme-y parens
Curator: <https://upbookclub.com> / Twitter: @BonfaceKilz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-04-23 13:32 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-20 8:24 What to do when a package is removed upstream Bonface Munyoki K.
2021-04-20 8:35 ` Tobias Geerinckx-Rice
2021-04-20 16:24 ` Leo Famulari
2021-04-23 9:53 ` Bonface Munyoki K.
2021-04-23 12:06 ` Ricardo Wurmus
2021-04-23 13:26 ` Bonface Munyoki K.
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).