unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Merging the purge-python2-packages branch
Date: Tue, 31 May 2022 22:54:10 +0200	[thread overview]
Message-ID: <86k0a1judp.fsf@gmail.com> (raw)
In-Reply-To: <87mtexr060.fsf@gmail.com>

Hi Maxim,

Thanks for this janitor work. :-)


On Tue, 31 May 2022 at 15:07, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

>> Well, as a hobbyist, I am fine with such purge.  As a scientific
>> practitioner using Guix at work, it is more annoying…
>
> Agreed.  My understanding is that scientists making use of Guix already
> use a variety of Guix channels, so I'd assume the now missing bits can
> be fitted in Guix-Past or a suitable place without causing too much of a
> change to their workflow.

This assumption about scientists is not rooted, IMHO.  What I can say is
that, in my lab, some people are still using python2- variants as ’bamm’
for example.  They are not packager and they have other fishes to fry;
they use Guix to have the things done, they are not hobbyists who like
tweaking their computational environment. :-)

If I do not transfer myself the packages or explain them how to reach
these packages (git log, find the commit, etc. because yes, some people
are still installing python2- variants for some specific tasks), then
they will probably have again another bad experience with Guix.

And no, 15 days is not enough time to move 602 packages (minus the
broken ones ;-)) from master to another channel as guix-past.

Some workflow will be broken, for sure.  Bah it is an habits when using
Guix, sadly. :-)


> So, I'll go ahead with the merge and we can go from there.  In the
> future, I'll try to remember to send a guix-devel message around the
> time the patches hit guix-patches :-).

Again, I totally agree with the purge.  But I disagree with the process.

Somehow, it is another data point showing it is hard to smoothly work in
production with Guix – some flavors are moving too fast for my taste [1].

Anyway!  The merge will be a double “darwinism” experience. ;-) Only the
most motivated* users with a broken workflow will accept such breakage.
Only the most relevant python2- variant packages will survive
elsewhere. :-)

*darwinism meaning here “selection”
*motivated by other unique Guix features

1: <https://yhetil.org/guix/86mtv29erk.fsf@gmail.com>


Cheers,
simon




  reply	other threads:[~2022-05-31 20:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 13:25 Merging the purge-python2-packages branch Maxim Cournoyer
2022-05-30 15:18 ` zimoun
2022-05-30 15:32   ` Maxim Cournoyer
2022-05-30 16:49     ` zimoun
2022-05-31  7:39       ` Reza Housseini
2022-05-31 19:07       ` Maxim Cournoyer
2022-05-31 20:54         ` zimoun [this message]
2022-06-01 16:21           ` Ludovic Courtès
2022-06-01 19:51             ` zimoun
2022-06-01 20:30               ` Maxime Devos
2022-06-02  7:25                 ` zimoun
2022-06-02  9:36                   ` Maxime Devos
2022-06-02 14:04               ` Ludovic Courtès

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=86k0a1judp.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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