Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 14:03, Julien Cristau wrote:
> On Tue, Feb 11, 2014 at 13:58:17 +0100, Daniel Pocock wrote:
>
>> On 11/02/14 13:44, Markus Wanner wrote:
>>> On 02/11/2014 01:40 PM, Julien Cristau wrote:
>>>> Please try to avoid versioned -dev packages. Unless you really really
>>>> have to keep both versions around for years.
>>> Why is that? Keep in mind this is a headers-only library, i.e. it only
>>> ever ships with a -dev (and a -doc) package. There's no other way
>>> multiple versions of this library can be installed on a system.
>>>
>> Julien, Fedora and EPEL6 still have 1.4.8 as well. We don't know how
>> widely it is used in things that are not packaged (e.g. in private code
>> that people run on Debian)
>>
> That's irrelevant, as far as I'm concerned.
Not exactly - upstreams may be less likely to adapt their code for v1.10
and that means we end up having to make more local patches or leaving
things out of Debian
However, I'll check with the Fedora maintainer for asio-devel, maybe
Fedora 21 can carry v1.10
>
>> If we release a versions libasio1.4-dev package and libasio1.10-dev
>> concurrently in jessie it will mean people can transition more slowly
>> but nothing will really break
>>
> And if you don't they can still use the old version, either through the
> old package or through an unpackaged local version. Shipping libraries
> in Debian only makes sense if Debian packages use them, IMO.
At the moment, there are 3 proper packages using the old version of
libasio-dev and none of the upstreams have shown enthusiasm for the new
version
My feeling is that abiword and reSIProcate will continue using
libasio1.4-dev in jessie while any new project will hopefully start with
libasio-dev 1.10
Reply to: