This is the mail archive of the
mailing list for the Cygwin project.
Re: New Cygwin 1.7.0-18 in release-2
- From: "Yaakov (Cygwin Ports)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 21 Jul 2008 18:42:26 -0500
- Subject: Re: New Cygwin 1.7.0-18 in release-2
- References: <20080717155516.GC5675@calimero.vinschen.de>
-----BEGIN PGP SIGNED MESSAGE-----
Corinna Vinschen wrote:
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
| might be a result of the fairly massive changes in Cygwin 1.7. I
| attached a list of the changes below. The latest changes are:
I've considered making the switch, as the new features in 1.7 (namely
IPv6 and wchar functions) would make porting *much* easier. It might
also provide the chance to finally close the gap between Ports and the
distro, and generally improve our packaging scheme at the same time.
OTOH I don't have only myself to think about; with all my packages, I
doubt that I'll be able to support 1.5 any more after I switch.
It would help if I could get some clarification on:
*) When 1.7 goes gold (and I don't mean binutils!), is the recommended
upgrade path going to be in the same (Windows) tree, or to start fresh
in a new directory?
*) Is gcc-4.3 in the near future for 1.7? Will gcc define
_GLIBCXX_USE_WCHAR_T? Will it provide shared libgcc, libstdc++, etc?
*) Is there a roadmap of what needs to be done for 1.7? I know you
don't want to provide a date, but some focus and perspective would be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----