From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.1.9814cfd8f693 (TEST)
Date: Sun, 19 Sep 2021 08:42:26 +0200 [thread overview]
Message-ID: <87k0jdf4ml.fsf@Otto.invalid> (raw)
In-Reply-To: <a289b828-ec3b-0f38-720f-c7dbdd2e6770@t-online.de> ("Hans-Bernhard =?utf-8?Q?Br=C3=B6ker=22's?= message of "Sun, 19 Sep 2021 02:49:42 +0200")
Hans-Bernhard Bröker writes:
> It _is_ very surprising for tarballs, though. Those are generally
> expected to be buildable without having to run autoconf, automake,
> gettext, etc.
To provide a different data point: I generally remove all obviously
generated files before even starting to look at the rest of the build if
I use a release tarball.
> I'm pretty sure the GNU coding standards have required
> it since day 1. Automake generates tons of makefile real estate just
> for this.
I don't see that requirement in the current document:
https://www.gnu.org/prep/standards/standards.html
There is a requirement that the sources for such files are provided
alongside the instruction on how to re-generate them.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-09-19 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 20:33 Ken Brown via Cygwin-announce
2021-09-18 15:33 ` Achim Gratz
2021-09-18 19:03 ` Chris Roehrig
2021-09-18 20:17 ` Ken Brown
2021-09-18 20:01 ` Denis Excoffier
2021-09-18 20:20 ` Ken Brown
2021-09-18 21:30 ` Thomas Wolff
2021-09-18 22:32 ` Ken Brown
2021-09-19 0:49 ` Hans-Bernhard Bröker
2021-09-19 6:42 ` ASSI [this message]
2021-09-19 12:27 ` Ken Brown
2021-09-19 13:32 ` Thomas Wolff
2021-09-19 14:42 ` Ken Brown
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=87k0jdf4ml.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).