This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Retiring setup.hint


On Oct 25 20:42, Jon Turney wrote:
> 
> 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'm still generating setup.hint files for the Cygwin package itself.

Please have a look into cygwin's cygport file.  Do we have an *easy*
replacement for creating test releases from cygport in the meantime?

Ideally I can simply call cygport with a --test parameter or some such
to create a test release.

As long as we don't have that, I'm inclined to veto the idea to drop
setup.hint.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: signature.asc
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]