From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: More checks for Makefile.am:assert-no-store-file-names ?
Date: Mon, 07 Sep 2020 16:07:45 -0700 [thread overview]
Message-ID: <87imcpfany.fsf@yucca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
When running "make dist" there are some checks run, such as checking for
hard-coded store paths.
Would it be a good idea to add this or a similar check to
etc/git/pre-push and/or guix lint?
Would it make sense to set up a job to run "make dist" on the build farm
to catch these problems?
# Make sure we're not shipping a file that embeds a local /gnu/store file name.
assert-no-store-file-names:
$(AM_V_at)if grep -r --exclude=*.texi --exclude=*.info \
--exclude=*.info-[0-9] --exclude=*.dot \
--exclude=*.eps --exclude-dir=bootstrap \
--exclude=guix-manual.pot --exclude=guix-manual.*.po \
--exclude=guix-cookbook.pot --exclude=guix-cookbook.*.po \
--exclude=guix-prettify.el \
--exclude=ChangeLog* \
--exclude=binutils-boot-2.20*.patch \
-E "$(storedir)/[a-z0-9]{32}-" $(distdir) ; \
then \
echo "error: store file names embedded in the distribution" >&2 ; \
exit 1 ; \
fi
Checking this more often could prevent:
bug#43005: make dist fails: "store file names embedded in the distribution"
It would be nice to catch these bugs earlier, especially when they are
low down on dependency chain!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2020-09-07 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 23:07 Vagrant Cascadian [this message]
2020-09-16 10:27 ` More checks for Makefile.am:assert-no-store-file-names ? Ludovic Courtès
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=87imcpfany.fsf@yucca \
--to=vagrant@debian.org \
--cc=guix-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 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).