all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Daniel Semyonov <daniel@dsemy.com>
Cc: emacs-devel@gnu.org
Subject: Re: README used by NonGNU packages "remotely" even though it's ignored
Date: Tue, 07 Jun 2022 21:41:46 +0000	[thread overview]
Message-ID: <87leu86tid.fsf@posteo.net> (raw)
In-Reply-To: <87ee00p8bz.fsf@dsemy.com> (Daniel Semyonov's message of "Tue, 07 Jun 2022 22:44:16 +0300")

Daniel Semyonov <daniel@dsemy.com> writes:

> Hi,
>
> I noticed that the description shown on the NonGNU ELPA website for my
> packages (swsw and vcomplete), as well as the description shown through
> Emacs when viewing a version of the packages that isn't installed
> locally is the content of the README file included in their respective
> repositories.  However, both packages explicitly ignore that file (using
> an '.elpaignore' file).

Ignored files specify what files should not be added to the package
tarball.

> When viewing the description of a locally installed version of the
> packages, the commentary is shown (as is expected).
>
> I wonder if this behavior is intended, and if so whether it is
> documented anywhere?

See [0].  By default the README file is used.  If you prefer to, it is
possible to configure using the commentary section.

[0] https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/README?h=elpa-admin#n132,

> Regards,
> Daniel



  parent reply	other threads:[~2022-06-07 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 19:44 README used by NonGNU packages "remotely" even though it's ignored Daniel Semyonov
2022-06-07 21:37 ` Stefan Monnier
2022-06-07 21:41 ` Philip Kaludercic [this message]
2022-06-07 22:24   ` Daniel Semyonov
2022-06-08  9:21     ` Philip Kaludercic

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

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

  git send-email \
    --in-reply-to=87leu86tid.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=daniel@dsemy.com \
    --cc=emacs-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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.