From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Liliana Marie Prikler <leo.prikler@student.tugraz.at>
Cc: 50077@debbugs.gnu.org, guix-devel@gnu.org,
Xinglu Chen <public@yoctocell.xyz>,
Andrew Tropin <andrew@trop.in>
Subject: Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)
Date: Thu, 02 Sep 2021 09:25:32 +1000 [thread overview]
Message-ID: <87sfynq2xm.fsf@zancanaro.id.au> (raw)
In-Reply-To: <456243eca955ecc83b26663ed4e7e22d5170f03d.camel@student.tugraz.at>
On Wed, Sep 01 2021, Liliana Marie Prikler wrote:
> TL;DR: I'm generally in favor of branching emacs support
> packages off, even if origins are to be inherited.
This is my preference, and there is precedent for this in Guix
already. I know of emacs-protobuf-mode and emacs-erlang which are
separate packages, but which reference the source of an existing
package (with (package-source protobuf) and (package-source
erlang), respectively).
I like how easy it is to discover Emacs packages by looking for
the emacs- prefix. Mu and notmuch already violate that prefix
expectation, moving their elisp into a separate output would be
further hiding the Emacs modes.
Carlo
next prev parent reply other threads:[~2021-09-01 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1629122681.git.public@yoctocell.xyz>
[not found] ` <dd24f426b72a1c590cbd71d2eaa66a75b559a9e7.1629122681.git.public@yoctocell.xyz>
[not found] ` <87o89owoi0.fsf@trop.in>
[not found] ` <87r1edvown.fsf@yoctocell.xyz>
[not found] ` <87lf4j8kux.fsf@trop.in>
[not found] ` <87r1ebm503.fsf@yoctocell.xyz>
[not found] ` <8735qozkt0.fsf@trop.in>
2021-09-01 12:05 ` [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.) Xinglu Chen
2021-09-01 12:48 ` Liliana Marie Prikler
2021-09-01 23:25 ` Carlo Zancanaro [this message]
2021-09-03 16:14 ` Xinglu Chen
2021-09-01 13:52 ` 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=87sfynq2xm.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=50077@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=public@yoctocell.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.
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).