This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: libunistring dll version bump
- From: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 21 Sep 2014 09:51:32 +0200
- Subject: Re: libunistring dll version bump
- Authentication-results: sourceware.org; auth=none
- References: <541E73E9 dot 80408 at xs4all dot nl>
On 21/09/2014 08:44, Erwin Waterlander wrote:
Hi,
There is a new upstream version of libunistring: 0.9.4. I have created
the new packages, but I have not uploaded them yet.
In the new version there is a version bump of the dll,
cygunistring-0.dll will be replaced with cygunistring-2.dll. So I expect
that when I upload the new packages, all packages that depend on
libunistring will break.
How is this normally handled?
Should I just upload the new packages?
leave old libunistring0 in place with all the 0.9.3-2 packages
Create new libunistring2 package for the new dll.
So new compilation will use libunistring2 and current programs
will continue to use libunistring0
See as example libglpkXX on
https://www.cygwin.com/packages/
I know one package that depends on libunistring: wcd. Jari Aalto
maintains it, but he is not responding.
How can I find all the packages that depend on libunistring?
looks on setup.ini (for both 32bit and 64bit)
There are ~ 4 packages
regards,
Ciao
Marco