From: zimoun <zimon.toutoune@gmail.com>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: 45632@debbugs.gnu.org
Subject: [bug#45632] [PATCH] guix package: Warn if uses has 'guix' package in profile.
Date: Thu, 7 Jan 2021 17:39:58 +0100 [thread overview]
Message-ID: <CAJ3okZ2zw1PFLF6MW9BtTV6C0Qfr2v=JfHVSsCSOPy8L--cg9Q@mail.gmail.com> (raw)
In-Reply-To: <20210103183202.11224-1-kuba@kadziolka.net>
Hi,
On Sun, 3 Jan 2021 at 19:33, Jakub Kądziołka <kuba@kadziolka.net> wrote:
>
> * guix/scripts/package.scm (warn-about-guix-in-profile): New procedure.
> (process-actions): Call WARN-ABOUT-GUIX-IN-PROFILE before executing
> transaction.
> ---
>
> Unresolved questions:
> - Is this the right place to put warn-about-guix-in-profile?
> - The warning message seems to be hard-wrapped. Is this the right
> line length?
> - Do we want to make this configurable? Some other warnings are, but in
> those cases it is the threshold that gets configured. In this case,
> there is no threshold.
What is the use case? I have missed some context.
For example, I have the package 'guix' in some of my profiles and I
would be annoyed to be warned. And I have it for good reasons. :-)
Once the story about extension is good enough, maybe the warning would
be a good advice, otherwise it could be confusing. IMHO.
All the best,
simon
next prev parent reply other threads:[~2021-01-07 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 18:32 [bug#45632] [PATCH] guix package: Warn if uses has 'guix' package in profile Jakub Kądziołka
2021-01-07 16:39 ` zimoun [this message]
2021-01-07 17:11 ` Jakub Kądziołka
2021-01-07 17:46 ` zimoun
2021-01-07 20:31 ` Ricardo Wurmus
2021-01-07 17:15 ` Tobias Geerinckx-Rice via Guix-patches via
2021-01-07 17:56 ` zimoun
2021-01-07 17:58 ` Jakub Kądziołka
2021-01-07 19:25 ` 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='CAJ3okZ2zw1PFLF6MW9BtTV6C0Qfr2v=JfHVSsCSOPy8L--cg9Q@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=45632@debbugs.gnu.org \
--cc=kuba@kadziolka.net \
/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).