[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#409563: ITP: thinkfinger -- library and utility for the SGS Thomson Microelectronics fingerprint reader



Hello!

This is for bug readers and d-d's information.

On Thu, 08 Feb 2007 14:24:55 +0100, Rafael Laboissiere wrote:
> * Luca Capello <luca@pca.it> [2007-02-08 12:04]:
>
>> On Thu, 08 Feb 2007 01:38:42 +0100, Guillem Jover wrote:
>> > Please do not include it in the lib package, it's a pain afterwards
>> > when a new version with a different soname is introduced and
>> > disallows parallel installation of those.
>> 
>> With my non-yet-skilled-library packager hat on, I don't see why one
>> should want to install an old binary version with the new library
>> one, as both are coming from the same source, thus the same version
>> number.
>
> I am not sure I understand your rebuttal above,

I was mostly focusing on:

- libthinkfinger0 is installed with tf-tool v0

- libhtinkfinger1 comes out and it contains tf-tool v1

Upgrading to libthinkfinger1 necessarily means that tf-tool v1 needs
to be upgraded as well (because they come from the same source and
version).

> but I think Guillem was referring to a scenario similar to the
> following:
>
> Package bar has Depends: libfoo0.  Let us say that the developers of
> libfoo release a new version with the SOVERSION bumped.  In Debian,
> the package will be called, say, libfoo1.  New packages, like
> e.g. baz, will depend on libfoo1.  Now, if bar is a legacy program
> and does not compile against libfoo1 (since backward
> incompatibilites may have been introduced), then it has to keep its
> dependency on libfoo0.

OK, now reading again Guillem's reply I clearly see the problem.
Mostly, I didn't see any other use for the fingerprint reader than
authenticating someone.  However, from [1] I can see that there're
already fingerprint projects other than authentication, e.g. a SANE
backend.

> If, by an error in design, libfoo1 and libfoo0 conflict with each
> other (e.g. by having both a binary /usr/bin/foo-tool), then it will
> be impossible to have both bar and baz installed in the system.
> That is the pain Guillem was referring to.

Full ACK, I agree that we need separate packages.

Thank to both for the explanation!

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://wiki.debian.org/FingerForce

Attachment: pgpr7ZTyMrxL2.pgp
Description: PGP signature


Reply to: