From: zimoun <zimon.toutoune@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>, 38529@debbugs.gnu.org
Subject: bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism
Date: Fri, 13 Dec 2019 17:32:33 +0100 [thread overview]
Message-ID: <CAJ3okZ1L_nmhdOwsxFmmTA3v9GiB=6NU2jSZFF7AgY-fctHtsA@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pgevGwP6+jSY-+0DPdtvK60sEvd-uibqhRawuo6N1pL-Q@mail.gmail.com>
Hi Gábor,
Sorry to be slow. :-)
On Fri, 13 Dec 2019 at 17:28, Gábor Boskovits <boskovits@gmail.com> wrote:
> So in a more algorithmic manner:
> 1. if ad-hoc and inputs-of is present at the same invocation: fail
> hard. (With an error like incompatible options present)
> 2. if only ad-hoc is present, then print a deprecation warning (yes,
> we could make this suspendable with an environment variable, like you
> described)
> 3. if only inputs-of present, then do the new behaviour.
> 4. if neither ad-hoc nor inputs-of present then
> a. if GUIX_ENVIRONMENT_DEPRECATED is 1: do the current behaviour,
> b. if GUIX_ENVIRONMENT_DEPRECATED is undefined, or is not 1: do the
> new behaviour.
>
> This would minimze friction, as there will be a few scripts falling under 4.
> This would also allow mirgating such scripts one by one. be defining
> GUIX_ENVIRONMENT_DEPRECATED to 1 in some startup file, and using
> GUIX_ENVIRONMENT_DEPRECATED=0 guix environment ... in scripts that are
> fixed to use the new syntax.
>
>
> What do you think?
I am perfectly aligned! :-)
It is exactly what I have tried to describe.
Sorry again for being slow.
Thank you.
Do you plan to implement it? Do I give a try?
All the best,
simon
next prev parent reply other threads:[~2019-12-13 16:32 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 [this message]
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
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='CAJ3okZ1L_nmhdOwsxFmmTA3v9GiB=6NU2jSZFF7AgY-fctHtsA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=38529@debbugs.gnu.org \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
/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).