On Mon, Jun 27, 2005 at 02:54:04PM +0200, Loïc Minier wrote:
[...]
> In summary, what I want is something like:
> debian/control: Depends: ${shlibs-depends}, libfoo (>= x.y)
> debian/substvars: shlibs-depends: libfoo (>= x.0)
>
> => DEBIAN/control: Depends: libfoo (>= x.y)
>
> Although I didn't find any lintian warning on double depends, I presume
> they're not particularly welcome.
W: aspell-bin: package-has-a-duplicate-relation depends: libaspell15 (>=
0.60),libaspell15 (= 0.60.2+20050121-3)
N:
N: The package seems to declare a relation on another package which is
N: already implied by other relations it declares, and is therefore
N: redundant.
N:
N: Note that when using ${shlibs:Depends}, this is sometimes unavoidable
N: (unless you're in a mood for ugly kludges), feel free to
N: ignore/override this warning in that case, as it can only be fixed at
N: the package-tools level (e.g., in dpkg)
> Side note: this would be particularly useful if I forget to bump the >=
> x.y dependency (which is generated anyway).
>
> If this can't be done easily, I'll resort to double-depends.
As the above indicates, that's pretty much the only solution for now...
> PS: in case you wonder why the shlibs aren't bumped, this is because
> upstream guarantees its interfaces, but might use some non-declared
> functions internally, ie. functions that are not in API headers, and
> expects binary packages not to mix upstream versions.
I found the exact same problem in my package above.
--
Society is never going to make any progress until we all learn to
pretend to like each other.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
