Re: libc6 vs. libc6.1/testing rather strange (broken ?)
Helge Kreutzmann <kreutzm@itp.uni-hannover.de> writes:
> Yesterday I came around an example which might explain part of the
> problem: dcraw
>
> I got the source, compiled it and tried to install it, however:
>
> Depends: libc6 (>= 2.3.2-1)
>
> Does this dependency have to read:
> Depends: libc6 (>= 2.3.2-1) | libc6.1 (>= 2.3.2-1)
>
> Should I fill bugs against such packages?
Yes. They should usually just use
Depends: ${shlibs:Depends}
or your version if they really need a specific libc version.
> Is the version numbering for libc6 and libc6.1 the same, i.e. do I have to wait
> for libc6.1 2.3.2-1 before I can use dcraw?
Yes, it's really the same package, only for weird historical reason
the package is called libc6.1 on Alpha and IA64 and libc6 everywhere else.
The explicit dependency in dcraw is probably just a mistake, though,
there is basically no reason why a source would not work with older
glibcs.
> (I removed the versioned dependency in this case but have not yet
> tried dcraw).
BTW, are you trying to hook up a digital camera to your Alpha? I'd be
interested in experiences :)
--
Falk
Reply to: