From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>, 38529@debbugs.gnu.org
Subject: Re: bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism
Date: Fri, 20 Dec 2019 12:24:00 +0100 [thread overview]
Message-ID: <m1fthfz1db.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <CAJ3okZ3zSS0Rbnu5eLhpYHPvSY1emaj=-estQcjRwiJ3=4RMMA@mail.gmail.com>
Hi Simon,
> Assuming "guix environment" would stay and following the proposed
> plan, you would need to add GUIX_ENVIRONMENT_DEPRECATED=1 on the top
> of your script. In this would not be a problem for travelling back in
> time.
The problem is not how I update my scripts - I can manage that, no
matter what it takes.
The problem is scripts circulating in public repositories, tutorials,
etc. New users will find them and use them for inspiration. It's very
discouraging to see examples from tutorials fail or do something weird.
The main precedent is the Python 2->3 transition. There are tons of
GitHub repositories with Python code but no indication if it's 2, 3, or
both. I even had to use one that executed with either 2 or 3, but gave
different results. It takes a lot of motivation to persist.
For guix, there's the additional issue that we use the reproducibility
of builds as an argument. Non-reproducible examples are then a bit of a
credibility problem.
Cheers,
Konrad.
next prev parent reply other threads:[~2019-12-20 11:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eexeu8mo.fsf@ambrevar.xyz>
[not found] ` <CAJ3okZ3WnG87m=jQw08M9ER+=9FS0NVx=uALHK_-4LuD50KhvA@mail.gmail.com>
2019-12-12 11:23 ` Make --ad-hoc the default for guix environment proposed deprecation mechanism Gábor Boskovits
2019-12-12 16:47 ` bug#38529: " zimoun
2019-12-12 20:54 ` Gábor Boskovits
2019-12-13 12:02 ` zimoun
2019-12-13 16:27 ` Gábor Boskovits
2019-12-13 16:32 ` zimoun
2019-12-13 16:41 ` Gábor Boskovits
2019-12-14 18:11 ` Hartmut Goebel
2019-12-16 22:09 ` Ludovic Courtès
2019-12-17 6:49 ` Konrad Hinsen
2019-12-17 9:14 ` Gábor Boskovits
2019-12-17 13:33 ` Kyle Meyer
2019-12-17 14:22 ` Brett Gilio
2019-12-17 22:30 ` Bengt Richter
2019-12-17 23:21 ` Bengt Richter
2019-12-17 17:07 ` zimoun
2019-12-18 9:43 ` Konrad Hinsen
2019-12-18 13:09 ` zimoun
2019-12-20 11:24 ` Konrad Hinsen [this message]
2019-12-20 12:03 ` zimoun
2019-12-20 21:08 ` Ricardo Wurmus
2019-12-23 9:28 ` Danny Milosavljevic
2020-01-02 9:49 ` Andy Wingo
2019-12-18 20:55 ` Arne Babenhauserheide
2019-12-19 11:30 ` zimoun
2019-12-19 21:39 ` Arne Babenhauserheide
2019-12-19 22:40 ` zimoun
2019-12-20 1:37 ` Arne Babenhauserheide
2019-12-20 11:40 ` zimoun
2019-12-20 23:02 ` Arne Babenhauserheide
2019-12-21 0:04 ` zimoun
2019-12-20 21:12 ` Ricardo Wurmus
2019-12-21 15:18 ` Konrad Hinsen
2019-12-19 16:31 ` Deprecating ‘guix environment’? Ludovic Courtès
2019-12-19 22:48 ` zimoun
2019-12-20 11:17 ` Konrad Hinsen
2019-12-20 13:21 ` zimoun
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=m1fthfz1db.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--cc=38529@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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).