From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Please "make distcheck" after largish changes
Date: 29 Dec 2002 13:40:25 +0100 [thread overview]
Message-ID: <87bs35athi.fsf@zagadka.ping.de> (raw)
Everybody, please make sure that "make distcheck" works after
commiting changes to the build system, or other changes.
The typical problem is that some new file is not included in the
distribution tarball, or that a new Makefile rule does not properly
work for a vpath build. These problems are normally easy to solve
when one is aware of them. Running "make distcheck" will test for
things like this.
The snapshots process runs "make distcheck" every night. I could sent
the logs for failed builds to <guile-devel@gnu.org> or some other
list. Would that be OK? The logs are quite large, depending on where
the build failed: up to 0.5MB. Alternatively, I could truncate the
logs to their last 100 lines, or so.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2002-12-29 12:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bs35athi.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
/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.
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).