From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: [ITP, RFU] Unison: new, updated, and obsoleted packages
Date: Fri, 06 Jul 2007 18:28:00 -0000 [thread overview]
Message-ID: <3s1t83ho95kfne31vkutab4tscbo8cgcn3@4ax.com> (raw)
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
needed.
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.
Thanks,
Andrew.
# unison2.27
wget \
http://home.comcast.net/~andrex/cygwin/unison2.27/setup.hint \
http://home.comcast.net/~andrex/cygwin/unison2.27/unison2.27-2.27.29-1.tar.bz2 \
http://home.comcast.net/~andrex/cygwin/unison2.27/unison2.27-2.27.29-1-src.tar.bz2
# unison2.17
wget \
http://home.comcast.net/~andrex/cygwin/unison2.17/unison2.17-2.17.1-2.tar.bz2 \
http://home.comcast.net/~andrex/cygwin/unison2.17/unison2.17-2.17.1-2-src.tar.bz2
# unison2.13
wget \
http://home.comcast.net/~andrex/cygwin/unison2.13/unison2.13-2.13.16-2.tar.bz2 \
http://home.comcast.net/~andrex/cygwin/unison2.13/unison2.13-2.13.16-2-src.tar.bz2
next reply other threads:[~2007-07-06 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 18:28 Andrew Schulman [this message]
2007-07-09 9:05 ` Corinna Vinschen
2007-07-09 10:23 ` Andrew Schulman
2007-07-09 10:32 ` Corinna Vinschen
2009-04-30 20:25 Andrew Schulman
2009-05-01 14:54 ` Christopher Faylor
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=3s1t83ho95kfne31vkutab4tscbo8cgcn3@4ax.com \
--to=schulman.andrew@epamail.epa.gov \
--cc=cygwin-apps@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).