From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] cygport 0.25.0-1
Date: Fri, 03 Nov 2017 19:11:00 -0000 [thread overview]
Message-ID: <20171103191100.1BqHLI0lDLCYR3PidreppHepAhuWVLUTOVJshFpJ3ds@z> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.25.0-1
cygport is the standard method for building and maintaining packages for
the Cygwin distribution.
This release adds 'package-test' and 'stage' commands, and cygclasses for
Meson and Ninja build systems, along with various bugfixes.
Achim Gratz (2):
perl: fix SUMMARY nomenclature
src_prep: report patch level used
Andrew Schulman (1):
check that Cygwin patchfile exists before asking to sign it
Ken Brown (1):
Honor the PKG_CONTENTS variable if it is set, even if it is empty
Yaakov Selkowitz (17):
prepstrip: skip executables containing Neko bytecode
python-wheel: use setuptools.launch
kde4: update kde-l10n handling for 17.04
kde4: handle splitup of calligra-l10n
perl: add CPAN_VERSION
ninja: new cygclass for packages building with ninja
meson: new cygclass for building with Meson on top of Ninja
pkg_pkg: ignore changes under host triplet directory
Add stage command for uploading without marking !ready
ninja: rename ninja_compile to cygninja
postinst: add latest Qt license filenames to prepdoc
qt5-qmake: do not use qmake -recursive
Add package-test command for marking test releases
bash-completion: add stage and package-test commands
list_deps: always use system cygcheck
Update gnuconfig
Bump version to 0.25.0
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2017-11-03 19:11 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=20171103191100.1BqHLI0lDLCYR3PidreppHepAhuWVLUTOVJshFpJ3ds@z \
--to=yselkowitz@cygwin.com \
--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).