unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com>
Cc: 50825@debbugs.gnu.org
Subject: bug#50825: 28.0.50; improve documentation for `define-package'
Date: Mon, 27 Sep 2021 06:13:17 +0200	[thread overview]
Message-ID: <87czoupsf6.fsf@gnus.org> (raw)
In-Reply-To: <87r1db44tm.fsf@gmail.com> (Michelangelo Rodriguez's message of "Sun, 26 Sep 2021 19:36:21 +0200")

Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com> writes:

>    One of the files in the content directory must be named
> ‘NAME-pkg.el’.".
> It should be clarified that, actually, the <name>-pkg.el is generated by
> the archive, and is not "responsibility" of the programmer that is
> actually writing the code.

These sections of the manual are directed at people managing an ELPA
repository, not towards people who are writing code that will end up
there.  So all the stuff about tar file names and -pkg files are things
ELPA repository maintainers need to know, but people that write the code
doesn't have to care about at all.

I've now added a paragraph to the Packaging node that explicitly says
this.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-09-27  4:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 17:36 bug#50825: 28.0.50; improve documentation for `define-package' Michelangelo Rodriguez
2021-09-27  4:13 ` Lars Ingebrigtsen [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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87czoupsf6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50825@debbugs.gnu.org \
    --cc=michelangelo.rodriguez@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/emacs.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).