gtkpod and dynamic libmp4v2

[Reinhard Tartler]

Maia Kozheva <sikon at ubuntu.com> writes:

> 28.04.2009 22:54, Reinhard Tartler wrote:
>> Maia Kozheva <sikon at ubuntu.com> writes:
>>> Response from gtkpod upstream:
>>>
>>>> I like the idea of dynamically detecting libmp4v2. Patches welcome.
>>> I'll try to write a patch this week and commit it to upstream SVN first, then
>>> backport to Ubuntu.
>>
>> Excellent, thanks for your work!
>
> I've committed the changes upstream and uploaded gtkpod version 0.99.14-2ubuntu2
> adding the patch. Now libmp4v2 support (and thus .m4a handling) should be
> enabled in gtkpod if libmp4v2-0 is installed. (I added it to recommends.)

Good work! You rock!

> I'm not sure what to do with the gtkpod-aac package, though. The user will get
> the same functionality with gtkpod and libmp4v2-0 installed, but even a
> transitional package cannot depend on the latter because it is in multiverse.
>
> I see two possible directions from here:
>
> 1) remove the current Ubuntu gtkpod-aac source package and add a transitional
> gtkpod-aac package to gtkpod that does not depend on libmp4v2-0;
> or 2) replace the gtkpod-aac package in multiverse (currently a modified copy of
> gtkpod) with a small native package that does nothing except pulling gtkpod and
> libmp4v2-0.
>
> Which approach would be preferable?

I think 1, but the other way round:

first add a gtkpod-aac transitional binary package to the gtkpod source
package, get that accepted. Since that version is higher than the old
gtkpod-aac source package, it will get always installed.

then wait for (or ping) the archive admins. They should automatically
detect that gtkpod-aac is obsolete and remove it from the archive.

approach 2 is IMO less desireable because it leaves us with 2 source
packages. One source package is clearly less cluttered and IMO more
obvious to manage.

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