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 14:34:49 -0600 [thread overview]
Message-ID: <87tvj9mf12.fsf@posteo.net> (raw)
In-Reply-To: <8736qttg3h.fsf@elephly.net>
Ricardo Wurmus writes:
> Hi Pierre,
>
>>> I am also in favor
>>> of renaming SBCL-Next to something else. I know that we are using sbcl
>>> instead of clisp for building it, but the naming scheme seems to imply
>>> an SBCL library or module rather than a web browser application.
>>
>> This is being discussed for stumpwm in bug #33311. […]
>
> I’ve read that discussion, but I don’t see how it is relevant.
> The *name* of the package surely does not have any effect on the
> features, does it?
>
> For applications like StumpWM and Next we could change the package names
> to “stumpwm” and “next”, respectively. That these packages can *also*
> be used as libraries does not mean that the packages should have names
> with the “sbcl-” or “cl-” or “other-lisp-” prefix.
>
> Am I misunderstanding something?
That was my understanding as well Ricardo. I do not see how renaming the
package would detach it from its respective compiler. It should still be
just as hackable in SLIME... Or so I thought?
Brett
next prev parent reply other threads:[~2018-12-19 20:34 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 [this message]
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
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=87tvj9mf12.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).