From: Ricardo Wurmus <rekado@elephly.net>
To: "Bonface Munyoki K." <me@bonfacemunyoki.com>
Cc: help-guix@gnu.org, Pjotr Prins <pjotr2020@thebird.nl>
Subject: Re: What to do when a package is removed upstream
Date: Fri, 23 Apr 2021 14:06:46 +0200 [thread overview]
Message-ID: <87bla5qk6h.fsf@elephly.net> (raw)
In-Reply-To: <86wnstjphl.fsf@bonfacemunyoki.com>
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
next prev parent reply other threads:[~2021-04-23 12:07 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
2021-04-20 16:24 ` Leo Famulari
2021-04-23 9:53 ` Bonface Munyoki K.
2021-04-23 12:06 ` Ricardo Wurmus [this message]
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=87bla5qk6h.fsf@elephly.net \
--to=rekado@elephly.net \
--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).