From: Stefan Kangas <stefankangas@gmail.com>
To: Lin Jian <me@linj.tech>, 73808@debbugs.gnu.org
Cc: philipk@posteo.net, Andrew Hyatt <ahyatt@gmail.com>,
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 21:29:59 +0000 [thread overview]
Message-ID: <CADwFkmk1jfnhXfPwevep9gEds-k80qRp8pr9EkKBoycL7=-9xQ@mail.gmail.com> (raw)
In-Reply-To: <874j5eiewq.fsf@linj.tech>
Lin Jian via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Some GNU ELPA packages include test files in their tarballs, such as
> triples[1]. Test files may have extra dependencies. For example,
> triples-test.el[2] requires kv. When installing package tarballs, those
> extra dependencies cause compilation errors, which causes package build
> failures in our NixOS CI.
>
> Given that users probably do not need those test files, I think it is a
> good idea to exclude them from tarballs. MELPA does that by default[3].
>
> WDYT?
The best way to exclude the test files is to add a .elpaignore file to
the upstream project. We can also do that on our end, but that makes it
less flexible for the package maintainer.
>
> [1]: https://elpa.gnu.org/packages/triples.html
> [2]: https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/triples-test.el?h=externals/triples&id=cf7f9c8dd77e47a1c32e0d0026df86a0eac4e2a5#n30
> [3]: https://github.com/melpa/melpa?tab=readme-ov-file#recipe-format
next prev parent reply other threads:[~2024-10-14 21:29 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 [this message]
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
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='CADwFkmk1jfnhXfPwevep9gEds-k80qRp8pr9EkKBoycL7=-9xQ@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).