This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7 packages
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 24 Apr 2008 16:28:13 +0200
- Subject: Re: 1.7 packages
- References: <firstname.lastname@example.org>
- Reply-to: cygwin-apps at cygwin dot com
On Apr 24 08:58, Yaakov (Cygwin Ports) wrote:
> * where can a list of practical changes between 1.5 and 1.7 be found?
Missing in this list are a couple of newly exported functions, namely:
- open_memstream, fmemopen, futimens.
- openat, faccessat, fchmodat, fchownat, fstatat, futimesat, linkat,
mkdirat, mkfifoat, mknodat, readlinkat, renameat, symlinkat, unlinkat,
> * can 1.7 be installed and/or run in parallel to 1.5, or is a separate
> box required?
In theory, you can do this on a single machine. Practically, setup
isn't quite up to the task right now. It still installes mount points
in the registry under the keys used by Cygwin 1.5.x. That's why I
suggest to use another machine, for instance in a VM. OTOH, if you
know what you do...
> * how is 1.7 to be installed?
> * how are 1.7 packages to be uploaded and organized?
Like the 1.5 packages, just in the parallel release-2 area.
> * for how long will maintainers be expected to maintain two sets of
Until we are all more or less confident that we can release 1.7 and
its packages to the world.
You don't have to generate new packages if your package doesn't depend
on any of the new features. Other than that, if your package is IPv6
capable, just not on Cygwin, or if your package is linked against
minires, or if your package uses static buffers of size PATH_MAX, you
should definitely generate new packages.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com