From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.1.9814cfd8f693 (TEST)
Date: Sun, 19 Sep 2021 15:32:17 +0200 [thread overview]
Message-ID: <79bb310f-17e9-2d43-6a7a-670795b6be70@towo.net> (raw)
In-Reply-To: <dea2560f-0012-0741-2f71-e9295c21891b@cornell.edu>
Am 19.09.2021 um 14:27 schrieb Ken Brown via Cygwin:
> On 9/19/2021 2:42 AM, ASSI wrote:
>>> 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.
>
> I'm not sure how much we should worry about the GNU standards for
> release tarballs. Those standards are written for GNU projects, which
> are supposed to run on many different systems. The cygwin package
> runs only on Cygwin.
>
> On the other hand, maybe we could do a better job of documenting how
> to rebuild a package from source via cygport.
And via git clone, please, because that's the way developers start if
they want to contribute to cygwin.
I still claim it's a bad idea to hide that script in a subdirectory; it
should at least reside in the top-level directory, so if someone sees a
script "auto..." there, it will be an attempt to proceed with.
>
> Ken
>
next prev parent reply other threads:[~2021-09-19 13:32 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
2021-09-19 12:27 ` Ken Brown
2021-09-19 13:32 ` Thomas Wolff [this message]
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=79bb310f-17e9-2d43-6a7a-670795b6be70@towo.net \
--to=towo@towo.net \
--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).