The Chromium browser has its own copy of minizip. It would be nice if
it could use libminizip.so.1 from a new libminizip1 package instead.
Thoughts? Do you think this worth working on? (If so, I can mock
something up.)
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Source: zlib
> Version: 1:1.2.3.4.dfsg-3
> Severity: wishlist
>
> The Chromium browser has its own copy of minizip. It would be nice if
> it could use libminizip.so.1 from a new libminizip1 package instead.
>
> Thoughts? Do you think this worth working on? (If so, I can mock
> something up.)
Please work with upstream on this (as the Chrome guys really ought to
have done...). This is not something that should be done as a Debian
local change and I don't feel I'd be adding anything to the process
compared to you working with upstream.
> Please work with upstream on this (as the Chrome guys really ought
> to have done...). This is not something that should be done as a
> Debian local change and I don't feel I'd be adding anything to the
> process compared to you working with upstream.
Makes sense. Thank you for your thoughtfulness.
For reference: Fedora’s minizip library package was introduced in
August, 2007 [1]. They use automake to build the package [2], so
probably what will be required here is to rewrite their Makefile.am to
fit in with upstream’s build system.
[1] http://cvs.fedoraproject.org/viewvc/rpms/zlib/devel/zlib.spec?view=co
[2] http://cvs.fedoraproject.org/viewvc/rpms/zlib/devel/zlib-1.2.3-autotools.patch?content-type=text/plain&view=co