This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: per-version hints proposal
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 18 Sep 2016 16:14:01 +0100
- Subject: Re: per-version hints proposal
- Authentication-results: sourceware.org; auth=none
- References: <8b4723b2-1bd5-3604-1deb-cfd0a1c7b9d9@dronecode.org.uk> <87intvaw8c.fsf@Rainer.invalid> <7be1e9ea-651f-877b-eef4-7754ce05e588@gmail.com>
On 18/09/2016 06:17, Marco Atzeri wrote:
On 17/09/2016 08:14, Achim Gratz wrote:
Jon Turney writes:
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is needed when versions have different dependencies.
To automate this problem out of existence, I suggest replacing the
setup.hint file in an upload with a package-version-release.hint file.
Since this is now moving into reality, the documentation in
https://cygwin.com/setup.html
has become out-of-date.
Regards,
Achim.
are we not yet missing an updated cygport release ?
Or a test one
Yes, this is only usable by people running cygport from git, currently.
After I wrote the documentation update, I found it needs to describe
the backwards-compatible use of setup.hint.
Given that, there didn't seem to be any harm in pushing the
documentation update now.
Achim,
I notice the section about postinstall scripts doesn't mention permanent
postinsall scripts at all.
Could you possibly provide a couple of paragraphs?