unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: 50589@debbugs.gnu.org
Cc: Andrew Tropin <andrew@trop.in>, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#50589] [PATCH] doc: Document how to handle bundled Emacs packages.
Date: Tue, 14 Sep 2021 21:17:32 +0200	[thread overview]
Message-ID: <077f16a3b7d856a90719760b644e5d2e3cf520f2.1631646830.git.public@yoctocell.xyz> (raw)

See discussion about this:

  <http://issues.guix.gnu.org/issue/50231>

* contributing.texi (Emacs Packages): Document how Emacs packages that are
  part of “standard” packages should be handled.
---
Not sure if «“standard” package» is the correct phrase, maybe someone
has better suggestions.

 doc/contributing.texi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index d1b77d7d05..6ba9907366 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -703,6 +703,14 @@ When encountering problems, it is wise to check for the presence of the
 file, and whether any dependencies and their versions listed therein are
 satisfied.
 
+Some Emacs package are part of other ``standard'' packages (e.g., the
+@file{notmuch.el} package is part of the official Notmuch tarball).  In
+theses cases, the Emacs package should be in it's own @code{emacs-}
+package, while the ``standard'' package should not contain the Emacs
+package.  E.g., the @code{emacs-notmuch} package only contains the Emacs
+package for Notmuch, while the @code{notmuch} package contains the other
+things---command line tools, C library, etc.
+
 @node Python Modules
 @subsection Python Modules
 

base-commit: a72519489f0178051b7049d5793d95d070ebef86
-- 
2.33.0







                 reply	other threads:[~2021-09-14 19:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=077f16a3b7d856a90719760b644e5d2e3cf520f2.1631646830.git.public@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=50589@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=zimon.toutoune@gmail.com \
    /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).