On Wed, Dec 07, 2011 at 12:30:06PM +0000, Simon McVittie wrote:
> Is libproc considered to be a public shared library or not?
And this, is really, the crux of the whole matter.
Is it? Was it supposed to be? Can it be?
Well, it seems that as there are at least 3 packages (maybe more) that
depend on the library, then it IS a public library; no matter the
intention etc of upstream.
Given that, it needs to be fixed and made into a proper and
well-behaving library package, so I'm proposing that:
* libproc be split into its own package, probably libprocfs0
* the library file will have a proper SONAME that is not connected to
the package version anymore
* shlibs will be updated to be >= the first version I do this
* If I can work out how multi-arch works, I'll make it fit that
* procps binary will depend on libprocfs0
* dev package will be libprocfs0-dev
Now, what do we do about the programs that current depend on that
library and have Depends: procps with no version? Obviously they will
be recompilied to link to the new library, but should I have
Breaks: xmem < 1.2.3, guymager < 4.5.6
in the new version or not?
Anything else that should happen?
- Craig
--
Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/ csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
