Sorting the jack build-dependency mess

[Reinhard Tartler]

On Mo, Okt 25, 2010 at 16:18:01 (CEST), Adrian Knoth wrote:

> On Sat, Oct 23, 2010 at 01:36:09PM -0300, Felipe Sateler wrote:
>
>> I'm not happy with the way currently we need to add alternative
>> build-depends on the different libjack implementations. Possible ways
>> out of this problem:
>> 
>> 1. Make all jack implementations provide: libjack-dev. This leaves us
>> with unversionable build-depends.
>> 2. Create a new virtual package, like we did with the binary. This
>> means many sourceful uploads.
>> 3. Create a dummy package libjack-dev that depends on the default
>> implementation, but allows libjack2 or any other future
>> implementation. Could eventually allow versioned depends, although
>> with a weird version number.
>> 
>> I'm not quite sure losing the versioning is bad... supposedly jack
>
> Given that we're in freeze, I'd go for 1. I actually went for it:
>
>    http://git.debian.org/?p=pkg-multimedia/jackd2.git;a=commitdiff;h=db510f905741fa2b541e7a371bcca105dcb695ca
>
>
> So this basically boils down to a new upload and a freeze exception.
>
>
> Unless there's really a need to discuss this in detail, I'd simply
> upload the new version today.

so you don't care about unversionable build-depends? this means that not
a single package in the archive can then do

Build-Depends: libjack-dev (>> $minimun_version)

anymore. given that there is a number of jack using packages I'd be
rather reluctant to do this step.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4