From mboxrd@z Thu Jan  1 00:00:00 1970
From: EuAndreh via Bug reports for GNU Guix <bug-guix@gnu.org>
Subject: bug#38529: Make --ad-hoc the default for guix environment proposed
 deprecation mechanism
Date: Mon, 30 Dec 2019 06:44:34 -0300
Message-ID: <87blrqp2pp.fsf@euandre.org>
References: <87eexeu8mo.fsf@ambrevar.xyz>
 <CAJ3okZ3WnG87m=jQw08M9ER+=9FS0NVx=uALHK_-4LuD50KhvA@mail.gmail.com>
 <CAE4v=phY+7CTKMf8Y3a9p4okfqtMGOWu9kd2Nu6oCJW8OsK3Lw@mail.gmail.com>
 <CAJ3okZ3+-yAfRpYDHz-jYONguOPWjff0iWZ_7NPEz6x5mbOO1w@mail.gmail.com>
 <CAE4v=piMnBhHWpbB60qMRnnDNwqkuddfNv7cEihr9+5-52k2OA@mail.gmail.com>
 <CAJ3okZ3gJDdDKWERLANp+7ueSirEZ7hH=YKa3nhCAzCzAz1TGg@mail.gmail.com>
 <CAE4v=pgevGwP6+jSY-+0DPdtvK60sEvd-uibqhRawuo6N1pL-Q@mail.gmail.com>
 <87k16vdise.fsf@gnu.org> <e992ac46-37b9-ba12-83cc-6694427acd31@fastmail.net>
 <CAJ3okZ0Fw=02cDwdn5GuiDCyUNOUY=YaGyrFyHE5qWsOQTLASQ@mail.gmail.com>
 <m1pngmrmst.fsf@khs-macbook.home> <87zhfp2w11.fsf@web.de>
 <CAJ3okZ3bHnOzOk2Cdtvh_NZbYGDfA+zzxrAsJk+7=gRYHaL7jw@mail.gmail.com>
 <871rt03shq.fsf@web.de>
 <CAJ3okZ3gwpjy2cgRj1iOtPX0cTSVBLoxSVaUBxnMEsMCVNUyFg@mail.gmail.com>
 <87zhfn3hgj.fsf@web.de>
 <CAJ3okZ2XTAbPp0m7TQqCEi_oz223HyBd0BZefRO4Q90xmni2mw@mail.gmail.com>
 <87tv5upttv.fsf@elephly.net> <87o8w1mxjt.fsf@gnu.org>
Reply-To: EuAndreh <eu@euandre.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:52323)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ilrbj-0006uy-TJ
 for bug-guix@gnu.org; Mon, 30 Dec 2019 04:45:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ilrbi-0002AN-PJ
 for bug-guix@gnu.org; Mon, 30 Dec 2019 04:45:03 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:54529)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1ilrbi-00029m-LW
 for bug-guix@gnu.org; Mon, 30 Dec 2019 04:45:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ilrbi-0007Sj-KW
 for bug-guix@gnu.org; Mon, 30 Dec 2019 04:45:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.38529.B38529.157769908628648@debbugs.gnu.org>
In-Reply-To: <87o8w1mxjt.fsf@gnu.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>, Ricardo Wurmus <rekado@elephly.net>
Cc: GNU Guix maintainers <guix-maintainers@gnu.org>, 38529@debbugs.gnu.org

Hello :)

Jumping in the discussion xD

Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> Yes, I think it is clear that we=E2=80=99d have to do this using all the =
tools
> at our disposal, including time.
>
> Konrad=E2=80=99s objection remains though: existing documents (papers, bl=
og
> posts, MOOCs, etc.) that mention =E2=80=98guix environment=E2=80=99 would=
 all of a
> sudden become wrong if we were to change the defaults of =E2=80=98guix
> environment=E2=80=99.  Even if we introduce a variable to restore the old
> behavior.
>
> Perhaps that=E2=80=99s unavoidable in the long run, but perhaps this is n=
ot the
> right time for this.

Wouldn't having a new name for the new behaviour avoid breakage in this
situation?

Suppose the path of adding new subcommand is chosen, and it is "guix
shell". Couldn't it adopt the new desired behaviour?

  guix shell foo --inputs-of bar     # new command
  guix environment bar --ad-hoc foo  # untouched old command

After the introduction of "guix shell", "guix environment" could become
deprecated, but no current usage of it would stop working, and no public
references to it in the internet would become misleading. "guix
environment" could say that is has been deprecated, and point to "guix
shell", but keep working the same way.

If desired, "guix environment" could be removed after X time of
deprecation has passed, but that would be optional.

What are the downsides? Am I missing something?

Thanks,
euandreh.