Re: Bug#669373: RFS: flactag/2.0.1-1 ITP #507876
Hi,
In article <[🔎] 4FAFEB52.9000004@pocock.com.au>,
Daniel Pocock<daniel@pocock.com.au> wrote:
> What does that mean in practice? As a way of being able to use either
> the new or the old XML web API? Or both libs working against the same
> XML web API, but some client applications have simply not been updated yet?
>
/ws/1 still exists, but is deprecated. And not fully functional in some
areas. However, I'm sure there will be applications still using libmb3
> With some packages, like libdb, this seems to be a reality: people have
> different versions of db files on disk (particularly if shared
> filesystems are involved), and they need to be able to work with them.
> Not every library (or package) is compelled to give such flexibility though
Exactly. Because the API between limbb3 and libmb4 is so radically different,
you can't expect all applications to be immediately updated to libmb4.
>> My current preferred strategy is:
>>
>> 1. When the next server version is released (this week) release libmb4.0.2
>> using the existing scheme
>>
>>
>
> I think a new server version may justify a libmb 4.1.0, just to
> emphasize something is changing
Well, it's only extensions to the web service, not major changes
particularly. 4.0.1 will still work with the new server, it just won't be
able to return any of the new information.
> I think that is fine, but it is also 100% valid if you use the SONAME
> libmusicbrainz.so.5
>
> I'd be interested to get feedback from other people who have more
> extensive experience of library packaging than myself though, I'm simply
> working from what I've read in the GNU libtool guide and the Debian
> library packaging guide.
Happy to work to 'best practices' if there is such a thing. However, given
how close the freeze is, ideally I just want to get libmb4 (or 5) and
flactag in as soon as possible if we can.
> I agree that is a priority - we can't wait for Debian to flush out the
> old lib (although we should aggressively encourage them to do so as it
> wouldn't be nice to see it in wheezy by mistake, given that the XML API
> is no longer supported by the musicbrainz.org web service)
Yes. However, that seems like a very slow process. So we have to try to
shortcut it if possible.
Andy
Reply to: