From: zimoun <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "\(" <paren@disroot.org>, Tobias Geerinckx-Rice <me@tobias.gr>,
58583@debbugs.gnu.org
Subject: [bug#58583] [PATCH 0/1] scripts: package: Forbid installation of the guix package.
Date: Thu, 03 Nov 2022 19:32:41 +0100 [thread overview]
Message-ID: <87v8nvanxy.fsf@gmail.com> (raw)
In-Reply-To: <87sfj0axlv.fsf@gmail.com>
Hi Maxim,
On jeu., 03 nov. 2022 at 11:03, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Referring to info '(guix) Package Naming', that doesn't seem to be a
> written rule; my rule of thumb here would be: if something exists to be
> used exclusively as a command, drop the language-specific prefix. If it
> is a library or both a library and a command, keep the prefix. In
> doubt, keep the prefix.
Yes, for sure. And I agree that we should follow as close as possible
this rule of thumb because it provides a good consistency.
My point is: the line is not always clear and for some packages we have
a grey area.
Another example, we have pandoc and ghc-pandoc. IIRC, these two
packages had been created for a similar reason as we are discussing
here; from my understanding.
All in all, I am convinced that raising an error when installing the
package named ’guix’ is not an appropriated patch for fixing the
confusion generated by the package named ’guix’.
Well, I have said my opinion and this patch is not a breaking change
revolutionizing the world neither. ;-) Feel free to push a patch
containing what you find appropriate.
Cheers,
simon
next prev parent reply other threads:[~2022-11-03 18:52 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 ` [bug#58583] [PATCH 0/1] " Maxim Cournoyer
2022-10-28 7:44 ` 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 [this message]
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
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=87v8nvanxy.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=58583@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
--cc=paren@disroot.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).