From: Brett Gilio <brettg@posteo.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Next browser finally on master!
Date: Wed, 19 Dec 2018 15:48:44 -0600 [thread overview]
Message-ID: <87r2edmblv.fsf@posteo.net> (raw)
In-Reply-To: <87y38lry1v.fsf@elephly.net>
Ricardo Wurmus writes:
> The naming scheme applies to packages that are primarily used as
> libraries. A package “foo” that is written in Python and also provides
> modules that can be imported in an interactive Python session will not
> be named “python-foo” when it is primarily used on its own.
Agreed here. I don't want to speak out of turn and am interested in what
Andy has to say here, but there are a few other Guix packages that do
not follow their naming conventions when they are intended to be used
alone. I think Idris is one. Perhaps it would confuse the end user if
they were to know whether they were getting libraries for the SBCL
environment to be able to hack on the package or if they were getting a
runtime executable to operate the package without the SBCL environment.
Brett Gilio
next prev parent reply other threads:[~2018-12-19 21:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:34 Next browser finally on master! Pierre Neidhardt
2018-12-05 14:40 ` Benjamin Slade
2018-12-05 16:13 ` Pierre Neidhardt
2018-12-06 0:15 ` swedebugia
2018-12-06 8:31 ` Pierre Neidhardt
2018-12-06 9:38 ` Andreas Enge
2018-12-06 14:03 ` Pierre Neidhardt
2018-12-06 18:23 ` Andreas Enge
2018-12-06 18:24 ` Pierre Neidhardt
2018-12-06 18:29 ` Pierre Neidhardt
2018-12-06 21:02 ` Pierre Neidhardt
2018-12-09 16:19 ` Pierre Neidhardt
2018-12-09 16:21 ` Pierre Neidhardt
2018-12-19 13:40 ` Ludovic Courtès
2018-12-19 14:37 ` Pierre Neidhardt
2018-12-19 13:37 ` Ludovic Courtès
2018-12-11 7:18 ` swedebugia
2018-12-11 7:46 ` Pierre Neidhardt
2018-12-11 8:13 ` swedebugia
2018-12-11 17:11 ` Pierre Neidhardt
2018-12-19 13:35 ` Ludovic Courtès
2018-12-19 18:47 ` Brett Gilio
2018-12-19 19:03 ` Pierre Neidhardt
2018-12-19 19:08 ` Pierre Neidhardt
2018-12-19 20:32 ` Brett Gilio
2018-12-19 20:29 ` Ricardo Wurmus
2018-12-19 20:34 ` Brett Gilio
2018-12-19 21:32 ` Pierre Neidhardt
2018-12-19 21:45 ` Ricardo Wurmus
2018-12-19 21:48 ` Brett Gilio [this message]
2018-12-19 22:07 ` Pierre Neidhardt
2018-12-19 21:45 ` Brett Gilio
2019-01-03 4:32 ` Andy Patterson
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=87r2edmblv.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.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.
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).