This is the mail archive of the
cygwin
mailing list for the Cygwin project.
cygport: testing for 0.2.7
- From: "Yaakov S (Cygwin Ports)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin at cygwin dot com, cygwin-ports-general at lists dot sourceforge dot net
- Date: Tue, 19 Dec 2006 01:20:14 -0600
- Subject: cygport: testing for 0.2.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I'm counting down to releasing 0.2.7. cygport developers, please cvs up
and test (especially PATCH_URI).
New features for 0.2.7:
* Use PATCH_URI for upstream or third-party patches; these patches are
included individually in the -src.tar.bz2 and do NOT get included in the
.src.patch. See ports/apps/vim/gvim-7.0.178-1 and
ports/gnome/imlib/imlib-1.9.15-1 for examples of usage.
* CYGWIN_PATCHES/(PKG_LIST[#]).list files can be used in place of
PKG_CONTENTS[#].
* Add gtk-update-icon-cache to postinstall as needed.
* New binary dependency method.
* cross.cygclass: NEW for cross-compilers and cross-compiling; NEEDS WORK.
* gst-plugins*: External-dep plugins in separate bin packages can be
built together with the internal-dep plugins.
* pygtk: Support new bindings in 2.16.
* mirrors: Add rotator to sourceforge; add portage and vim.
* doc: HTML version of cygport.1.
Bug fixes:
* Handle HTTPS URIs with invalid certificates.
* Ignore mdate-sh in pkg_diff().
* Preserve shell metacharacters in args (Eric Blake).
* Fix AC_CONFIG_SUBDIRS and AC_CONFIG_HEADERS again.
* fox: Restore doxygenation.
* perl: Handle (incorrect) use of site_perl.
* ruby: Fix definition of RUBY_ARCH.
* ruby-gnome2: multiple build fixes.
Yaakov
Cygwin Ports
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFh5KupiWmPGlmQSMRCH+FAKClBVODy/ql54Tf1pAuNr/cFacK9QCdG/RB
u7m8teBQ75/rTIqVjnitdEA=
=ZnOb
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/