all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: the upcoming Great Python2 Purge™
Date: Mon, 18 Feb 2019 17:30:32 +0100	[thread overview]
Message-ID: <m1k1hxxdnb.fsf@fastmail.net> (raw)
In-Reply-To: <87h8d1we1v.fsf@elephly.net>

Hi Ricardo,

>> "My channel" doesn't exist (because I haven't yet found the time to
>> figure out how to set up and manage a channel, although it's been on my
>> to-do list for a while).
>
> I’d be happy to assist.

Thanks! I might come back to that offer when I find at least enough time
to figure out precisely what information I might be lacking
(that's meta-lack-of-time).

>> But... how about splitting off *all* of Python 2 and everything that
>> depends on it into a separate channel, which would then be maintained
>> by a separate team?
>
> Currently this is not feasible, in my opinion, as a lot of packages in
> Guix still depend on Python 2 for some reason or the other.  When Python
> 2 reaches EOL, however, I think this would be a reasonable thing to do.

Sounds good, then the only remaining issue is defining a transition
protocol. What I'd like to avoid is that packages disappear one by one
from Guix and then have to be dug out one by one from Git history for
setting up a Python 2 channel.

More generally, I think it would be useful to collect in some place all
package definitions that are removed from Guix. For example, a list with
package names plus the last Guix commit that had the package.

Konrad.

  parent reply	other threads:[~2019-02-18 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26  9:38 the upcoming Great Python2 Purge™ Efraim Flashner
2018-12-26 12:30 ` Marius Bakke
2018-12-26 13:33   ` add DEPRECATION grace period: " Pjotr Prins
2018-12-27  4:47     ` Leo Famulari
2018-12-27 15:52       ` Alex Vong
2018-12-27  4:50   ` Leo Famulari
2018-12-26 19:47 ` Konrad Hinsen
2018-12-27  4:38 ` Leo Famulari
2018-12-27 14:49   ` Brett Gilio
2019-02-18  9:56 ` Efraim Flashner
2019-02-18 10:16   ` Konrad Hinsen
2019-02-18 10:29     ` Ricardo Wurmus
2019-02-18 11:02       ` Konrad Hinsen
2019-02-18 11:07         ` Ricardo Wurmus
2019-02-18 14:42           ` zimoun
2019-02-18 16:30           ` Konrad Hinsen [this message]
2019-02-18 16:54             ` the upcoming Great Python2 Purge�?� ng0
2019-02-18 19:27             ` the upcoming Great Python2 Purge™ zimoun
2019-02-18 18:38   ` Brett Gilio
2019-02-18 21:39   ` Björn Höfling

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=m1k1hxxdnb.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.