Hey,
> Ok, getting dependencies "right by default" is as good a reason as any
> to support it the conceptual idea (among other because strictly-equal
> version dependencies are fine between same-source binaries).
great, that you understand what I want and why this is helpful. I have often
proble
Hey,
> Ok, getting dependencies "right by default" is as good a reason as any
> to support it the conceptual idea (among other because strictly-equal
> version dependencies are fine between same-source binaries).
great, that you understand what I want and why this is helpful. I have often
proble
Sandro Knauß:
> Control: tags -1 - moreinfo
>
> Hey,
>
>> Can you expand a bit on the use case here or the problem you want to
>> solve? At the moment, I cannot see how it is different from having the
>> following in your d/control file
>>
>> """
>> Depends: other-package (= ${binary:Version}),
Control: tags -1 - moreinfo
Hey,
> Can you expand a bit on the use case here or the problem you want to
> solve? At the moment, I cannot see how it is different from having the
> following in your d/control file
>
> """
> Depends: other-package (= ${binary:Version}), ...
> """
>
> (Except this
Control: tags -1 moreinfo
On Thu, 10 Oct 2019 20:49:11 +0200 =?utf-8?q?Sandro_Knau=C3=9F?=
wrote:
> Package: debhelper
> Version: 12.6.1
> Severity: wishlist
>
> You may end up in a situation, where you want a very strict dependency
> the binary packages of a related packages. This feature is cu
Package: debhelper
Version: 12.6.1
Severity: wishlist
You may end up in a situation, where you want a very strict dependency
the binary packages of a related packages. This feature is currently
developed in pkg-kde-tools, but may also be interesting for other
library packages.
The code is develop
6 matches
Mail list logo
