RFS: wcslib

2011-09-24 Thread Ole Streicher
regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r536m8ns@news.ole.ath.cx

Shared libs dependencies

2011-09-23 Thread Ole Streicher
Dear list, I am a bit confused about how I have to declare the dependencies when creating a shared library package. I've read the Debian Policy Manual; however I do not now understand what to do. First of all: what is the difference between the Depends field in the control file and the shlibs

Re: Package separation/naming conventions

2011-09-23 Thread Ole Streicher
Gergely Nagy alger...@balabit.hu writes: * Either don't build the part which (build-)depends on non-free, and don't ship it at all, then both the source and the resulting binaries can be in main. I will probably go with this option. If one really needs the libpgsbox, I would create a

Re: Shared libs dependencies

2011-09-23 Thread Ole Streicher
Gergely Nagy alger...@balabit.hu writes: Or, to put it in other words: Depends lists the packages your library depends on, shlibs lists the libs that packages built against your lib should depend on. So, this means that in the usual cases (like my one) this file looks like libwcs 4 libwcs4 (=

Re: Shared libs dependencies

2011-09-23 Thread Ole Streicher
Gergely Nagy alger...@balabit.hu writes: Ole Streicher debian-de...@liska.ath.cx writes: libwcs 4 libwcs4 (= 4.8.1-1) debian/libwcs4.shlibs should be the line you wrote above. It would be good if the policy would use the same naming conventions as the debhelper. Currently, the Debian Policy

Re: Package separation/naming conventions

2011-09-23 Thread Ole Streicher
Jakub Wilk jw...@debian.org writes: * Ole Streicher debian-de...@liska.ath.cx, 2011-09-23, 13:58: My question is not the naming of the binary packages. The original library is called wcslib, and to maximize confusion, there exists somewhere else another (not compatible, less used) library

Re: Package separation/naming conventions

2011-09-22 Thread Ole Streicher
Jakub Wilk jw...@debian.org writes: * Ole Streicher debian-de...@liska.ath.cx, 2011-09-21, 16:42: - libwcs4 and libwcs4-dev - libpgsbox4 and libpgsbox4-dev First of all, don't version your -dev package(s), unless you want to keep multiple versions of it in the archive at the same people. (You

Re: Package separation/naming conventions

2011-09-22 Thread Ole Streicher
Hi Ansgar, Ansgar Burchardt ans...@debian.org writes: Ole Streicher debian-de...@liska.ath.cx writes: Is the division into main and contrib done automatically based on the dependencies to non-free packages? No, it is done by hand using the Section field in debian/control. OK, so I have

Re: Package separation/naming conventions

2011-09-22 Thread Ole Streicher
Jakub Wilk jw...@debian.org writes: A -dev package should have a strict versioned dependency on all the shared libraries it provides .so symlink for. This is clear, but means that the wcslib-dev would depend on libpgsbox4, and therefore on pgplot5, which is not nice. libpgsbox.a would contain

Package separation/naming conventions

2011-09-21 Thread Ole Streicher
Dear list, I am currently packaging the wcslib package (Bug #641624) as my first Debian package, and I am wondering about the naming conventions. The package contains two libraries, some tools and an common API documentation for both libraries. I would now make the following binary packages: -

<    1   2   3