From: Andy Patterson <ajpatter@uwaterloo.ca>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Next browser finally on master!
Date: Wed, 2 Jan 2019 23:32:09 -0500 [thread overview]
Message-ID: <20190102233209.4d0f7414@mailservices.uwaterloo.ca> (raw)
In-Reply-To: <87zht1i4nt.fsf@ambrevar.xyz>
Hi,
Sorry for taking so long to chime in.
On Wed, 19 Dec 2018 22:32:22 +0100
Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> [...]
>
> That would not be consistent with the Lisp library naming scheme then.
> And it raises the question as to why we have bothered with the sbcl-
> and ecl- prefixes so far.
>
> Andy, any opinion on this?
>
That information is there to make sure that the transformer which
converts sbcl packages to source and ecl packages works properly. If
it's not being used, then there's no need to follow it. Even when it is
being used, it's always possible to manually override the name of the
final package - the convention is only there to make package name
transformation automatic. So if it's more desirable in a given
situation to use a non-conforming name, there's nothing that will
prevent you from doing so.
Hoping that helps,
--
Andy
prev parent reply other threads:[~2019-01-03 5:33 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
2018-12-19 22:07 ` Pierre Neidhardt
2018-12-19 21:45 ` Brett Gilio
2019-01-03 4:32 ` Andy Patterson [this message]
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=20190102233209.4d0f7414@mailservices.uwaterloo.ca \
--to=ajpatter@uwaterloo.ca \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).