From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: cygport 0.35.0-1
Date: Mon, 2 May 2022 21:51:21 +0100 [thread overview]
Message-ID: <9b79ae08-4ad7-bf0e-0623-ef7faf6a714c@dronecode.org.uk> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.35.0-1
cygport is the standard method for building and maintaining
packages for the Cygwin distribution.
Highlights of this release:
* New subcommands 'vars' and 'srcpackage'
* cygtest() no longer ignores errors from 'make check' (making the
default src_test function consistent with more specialized versions)
* Automatic dependency detection now generates a dependency on the
perl5_0xy provide for packages which install files into a versioned
vendor_perl directory or link with cygperl5_xy.dll.
Shortlog:
Achim Gratz (2):
cygclass/perl.cygclass: do not clobber HOMEPAGE and provide a
correct default
lib/pkg_info.cygport: implement automatic determination of the
appropriate perl5_0xy requirement
Adam Dinwoodie (1):
autotools.cygclass: correctly detect Autoconf 2.70+
Jon Turney (11):
Updates to tests for further rusting of python2
CI: Don't use a relative path with hashfiles()
testsuite: Add more expected hints
Don't ignore errors from make in cygtest()
Add 'vars' command to output arbitrary .cygport variables
Add srcpackage command
Add git-archive-all to build-depends
Updates to tests for package updates
xorg.cygclass: Allow configuration of default SRC_URI compression
autotools.cygclass: Report an error if ./configure version could
not be detected
Bump version to 0.35.0
reply other threads:[~2022-05-02 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9b79ae08-4ad7-bf0e-0623-ef7faf6a714c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-announce@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).