From: Xinglu Chen <public@yoctocell.xyz>
To: Andrew Tropin <andrew@trop.in>
Cc: 50077@debbugs.gnu.org, guix-devel@gnu.org
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: Wed, 01 Sep 2021 14:05:40 +0200 [thread overview]
Message-ID: <874kb4lcvf.fsf@yoctocell.xyz> (raw)
In-Reply-To: <8735qozkt0.fsf@trop.in>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
On Wed, Sep 01 2021, Andrew Tropin wrote:
> On 2021-08-30 15:33, Xinglu Chen wrote:
>
>> On Mon, Aug 30 2021, Andrew Tropin wrote:
>>
>>>> Why would it be more consistent to make a separate package? Making a
>>>> separate package is usually used for packaging a slightly different
>>>> version of the “regular” package, e.g., ‘emacs-next-pgtk’ adds native
>>>> compilation and pure GTK support for Emacs., ‘emacs-no-x’ removes X
>>>> suport for ‘emacs’. ‘emacs-notmuch’ isn’t really a different version of
>>>> ‘notmuch’, it’s just ‘notmuch’ but with all the non-Elisp stuff
>>>> removed. This is usually what using different outputs tries to achieve,
>>>> e.g., separate documentation from the main package, or in this case,
>>>> separate Elisp stuff from the main package.
>>>>
>>>
>>> Almost all elisp packages in Guix have a emacs- prefix, so as a user I
>>> expect to find notmuch*.el in emacs-notmuch package and notmuch binary
>>> in notmuch package, despite the fact that upstream distributes the
>>> source code for both of them in one tarball.
>>
>> Good point, however, If we were to have separate ‘emacs-’ packages for
>> the packages that also contain Elisp stuff, should those packages still
>> include the Emacs package in their output, i.e., should the ‘notmuch’
>> package still include notmuch.el, or should the Elisp stuff only be in
>> ‘emacs-notmuch’?
>>
>
> IMO, notmuch package should not include Elisp stuff, at least I don't
> see use cases, where it can be useful, but see where it can be
> harmful.
Should this apply to other packages that contains Elisp stuff too, or is
it specific to ‘notmuch’?
Cc’ing guix-devel to see what other people think before we start
breaking people’s setups. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next parent reply other threads:[~2021-09-01 12:06 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 ` Xinglu Chen [this message]
2021-09-01 12:48 ` [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.) Liliana Marie Prikler
2021-09-01 23:25 ` Carlo Zancanaro
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=874kb4lcvf.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=50077@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.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).