unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Lin Jian <me@linj.tech>
Cc: Andrew Hyatt <ahyatt@gmail.com>,
	philipk@posteo.net, 73808@debbugs.gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#73808: 30.0.91; Should test files be included in GNU ELPA tarballs?
Date: Mon, 14 Oct 2024 15:11:57 -0700	[thread overview]
Message-ID: <CADwFkmm+fv_yVp9T2JjHX+sa=vDJ+yozg-YQqx6iJf6etAV3cw@mail.gmail.com> (raw)
In-Reply-To: <87ttdegybs.fsf@linj.tech>

Lin Jian <me@linj.tech> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> The best way to exclude the test files is to add a .elpaignore file to
>> the upstream project.
>
> Agreed.  What about adding some documentation about this?

The below text has been added in Emacs 30 to
(info "(elisp) Multi-file Packages")

       If your package contains files that you don't wish to distribute
    to users (e.g. regression tests), you can add them to an
    ‘.elpaignore’ file.  In this file, each line lists a file or a
    wildcard matching files; those files should be ignored when
    producing your package's tarball on ELPA (*note Package Archives::).
    (ELPA will pass this file to the ‘tar’ command via the ‘-X’
    command-line option, when it prepares the package for download.)





  reply	other threads:[~2024-10-14 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 20:54 bug#73808: 30.0.91; Should test files be included in GNU ELPA tarballs? Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 21:29 ` Stefan Kangas
2024-10-14 21:37   ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 22:11     ` Stefan Kangas [this message]
2024-10-14 22:37       ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14 23:03         ` Stefan Kangas

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='CADwFkmm+fv_yVp9T2JjHX+sa=vDJ+yozg-YQqx6iJf6etAV3cw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=73808@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=me@linj.tech \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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).