From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: Retiring setup.hint
Date: Mon, 13 Nov 2017 19:59:00 -0000 [thread overview]
Message-ID: <70127913-6d64-4b65-eba5-9fe2671b0b9c@towo.net> (raw)
In-Reply-To: <c02c6bce-39f5-a636-475a-2a9ed066a404@dronecode.org.uk>
Am 25.10.2017 um 21:42 schrieb Jon Turney:
>
> I propose that calm will stop accepting uploads containing setup.hint
> some time shortly after 2017-11-18.
>
> This is approximately one year after the cygport release [1] which,
> stopped generating these files, so if you're using cygport >= 0.23.0,
> no action is needed.
>
> Warnings that you need to upgrade cygport have been generated for more
> than 6 months [2].
>
> After setup.hint uploads are disabled, any remaining setup.hint in the
> cygwin release on sourceware.org will be migrated to pvr.hint(s), as
> per [3].
>
> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
I would appreciate to see some explanation about this. Why the change
and what are package maintainers expected to do?
If calm can simply "rename setup.hint to pvr.hint", what's the purpose
of all this?
Thomas
next prev parent reply other threads:[~2017-11-13 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 19:42 Jon Turney
2017-10-25 20:23 ` Corinna Vinschen
2017-10-25 20:47 ` Jon Turney
2017-10-25 21:18 ` Corinna Vinschen
2017-11-13 11:39 ` Jon Turney
2017-11-13 13:39 ` Corinna Vinschen
2017-10-26 5:49 ` Achim Gratz
2017-11-13 19:59 ` Thomas Wolff [this message]
2017-11-13 20:14 ` Achim Gratz
2017-11-14 12:20 ` Jon Turney
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=70127913-6d64-4b65-eba5-9fe2671b0b9c@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@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).