From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "\(" <paren@disroot.org>, 58583@debbugs.gnu.org
Subject: [bug#58583] [PATCH 0/1] scripts: package: Forbid installation of the guix package.
Date: Thu, 27 Oct 2022 16:04:19 -0400 [thread overview]
Message-ID: <87ilk5hw3g.fsf_-_@gmail.com> (raw)
In-Reply-To: <874jw2l3m6.fsf@gmail.com> (zimoun's message of "Mon, 17 Oct 2022 20:14:09 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> writes:
> Hi,
>
> Cool! Nice initiative.
>
> On lun., 17 oct. 2022 at 17:50, "\( via Guix-patches" via <guix-patches@gnu.org> wrote:
>
>> + (report-error (G_ "the 'guix' package should not be installed~%"))
>
> Instead of an error, I would prefer a warning. Because, sometimes it is
> useful to have this Guix library. :-)
The Guix API would be available without having to 'guix install guix' in
the first place, no?
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-10-27 20:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 12:16 [bug#58583] [PATCH 0/1] scripts: package: Forbid installation of the guix package ( via Guix-patches via
2022-10-17 12:18 ` [bug#58583] [PATCH 1/1] " ( via Guix-patches via
2022-10-17 12:22 ` [bug#58583] [PATCH v2] " ( via Guix-patches via
2022-10-17 16:24 ` Tobias Geerinckx-Rice via Guix-patches via
2022-10-17 16:43 ` ( via Guix-patches via
2022-10-17 16:50 ` [bug#58583] [PATCH v3] " ( via Guix-patches via
2022-10-17 18:14 ` zimoun
2022-10-27 20:04 ` Maxim Cournoyer [this message]
2022-10-28 7:44 ` [bug#58583] [PATCH 0/1] " zimoun
2022-10-28 14:31 ` ( via Guix-patches via
2022-10-28 15:47 ` Maxim Cournoyer
2022-10-28 16:20 ` Tobias Geerinckx-Rice via Guix-patches via
2022-10-28 17:01 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-02 11:47 ` zimoun
2022-11-02 13:19 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-02 15:48 ` zimoun
2022-11-03 15:03 ` Maxim Cournoyer
2022-11-03 18:32 ` zimoun
2022-10-27 20:11 ` Maxim Cournoyer
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=87ilk5hw3g.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=58583@debbugs.gnu.org \
--cc=paren@disroot.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 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.