This is the mail archive of the
mailing list for the Cygwin project.
[ITP, RFU] Unison: new, updated, and obsoleted packages
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 06 Jul 2007 14:27:42 -0400
- Subject: [ITP, RFU] Unison: new, updated, and obsoleted packages
I have several changes for the Unison packages in Cygwin:
* All of the unison* packages now use a cygport build method. This is the
first time I've used cygport with unison*, so someone may want to review
that part. It works fine for me.
* New package: unison2.27. This is a new package for Cygwin, because it's
an incompatible version with the other unison* packages. But it's still
Unison, with the same package layout as all of the other unison* packages.
So I don't think any package review is needed, except possibly for the
cygport build script as described above.
* Updated packages: unison2.13, unison2.17. These have updated README.Cygwin
files and now use a cygport build method.
* Obsoleted packages: unison2.9.1, unison2.9.20, unison2.10.2, unison2.12.0.
- I looked in Debian, Fedora, openSuSE, and OpenBSD, and none of them are
still using these versions-- all have moved on to 2.13 or later.
- Upstream source is no longer available for all of them except 2.9.1, and
that version was pretty buggy.
- I asked three days ago on the cygwin list if anyone still needed these
packages and why, and I didn't hear anything to make me think they're still
Question: what should I do about these obsolete packages? I could release
new setup.hints for them with category: _obsolete, but would that force users
to uninstall them the next time they updated? I don't want to maintain those
packages any more, but I don't want to force users to uninstall them either.