From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Bonface Munyoki K." <me@bonfacemunyoki.com>
Cc: Pjotr Prins <pjotr2020@thebird.nl>, help-guix@gnu.org
Subject: Re: What to do when a package is removed upstream
Date: Tue, 20 Apr 2021 10:35:10 +0200 [thread overview]
Message-ID: <8735vle4ld.fsf@nckx> (raw)
In-Reply-To: <8635vlwegf.fsf@bonfacemunyoki.com>
[-- 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 --]
next prev parent reply other threads:[~2021-04-20 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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.
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=8735vle4ld.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=pjotr2020@thebird.nl \
/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.
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).