Bug#413987: Openjpeg updates
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robin Cornelius wrote:
> I have had a quick play with openjpeg today. On AMD64 i cannot run v1.2
> i need SVN newer than v1.2 due to very nasty bugs. I have added a patch
> to the dpatch system that brings version 1.2 upto SVN 465. I have also
> rebased the other patches required on the Makefile (one was dropped as
> its included in SVN). The so name is not quite right i *think* it should
> be 1.2.0.so.2 which is what i have it as now in the debian source.
Hmm. Where'd you get this numbering scheme from? A brief check of
the libs on my system suggests that libthing.so.major.minor is
normal for the actual shared library, ldconfig will create
libthing.so.major, and the -dev package has a link from libthing.so
to libthing.so.major.
(Note that Debian policy requires the libthing.so.major link to be
provided in the package as the library may be needed before ldconfig
has been run)
Also, that's not the soname. The soname is libthing.so.major.
Have you seen dancer's shared library packaging guide? I don't think
he dictates a name for the actual library, but the links libthing.so
and libthing.so.major are important to the Linux shared library loader.
I think it's best to reserve digits before the .so for API bumps
where the old API version is still under
development/maintenance/usage, ie. it would need a distinct -dev
package.
The only other numbering scheme I've seen, which is what upstream
uses before my dpatch, is libthing-major.minor.so. This would also
be fine, since ldconfig again can produce libthing.so.major, since
ldconfig doesn't use the _name_ of the file to determine that name,
but the -soname parameter to the linker. (See the upstream Makefile)
Out of curiosity, why are all your patches numbered 00?
A quick look at the .diff.gz file shows the following files have
been left lying around outside the debian/ directory:
openjpeg_svn_475.patch
patches/series
.pc/.version
(That last one might need to be added to a clean rule... I'm
guessing pkg-config has left it lying around)
It also looks like I left the 'debian/tm' file lying around,
better remove that in your next build.
Feel free to take over maintainership of this package if you
wish, or if you want to hook up a mailing list for maintainership
and make yourself an Uploader, I'm good with that too.
- --
- -----------------------------------------------------------
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
Very-later-year Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Pobox.com
Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
-- Kristian Wilson, Nintendo, Inc, 1989
License: http://creativecommons.org/licenses/by/2.1/au/
- -----------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHOkRWexDuohKLFuARAlUUAKC7UHE9JHEJdd2mdRtxxE7zNqDqpwCfazUd
sqcD7AdWKeIfQ959e2skWQs=
=Fn6Q
-----END PGP SIGNATURE-----
Reply to: