gtkpod and dynamic libmp4v2

[Maia Kozheva]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

11.05.2009 01:10, Reinhard Tartler wrote:
> 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.
> 

The issue with a transitional package (as brought up by James Westby) would be
that, being in universe, it wouldn't be able to pull libmp4v2 from multiverse.
So, hypothetically, users who install gtkpod-aac on a fresh system with
multiverse disabled won't get the expected AAC support.

Although the package description would clearly label it as transitional. Hmm...

Incidentally, are universe packages allowed to recommend (as opposed to suggest)
multiverse packages?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJKBxo8AAoJEE5B3XwSZmwBQ1oIALHSmoiHuzMNJry/I5/+dF/Z
CiF8627vrOSzL2Mjxv03m7KbuI2JCjrQ4MNPmhnib8SWea7zNjjMncriS9U77dng
7vRjvw7Ly8G7zLwDwI/4nBYG1NXapkbUMvCZDoWZewq22B2snRUij2tcIEAN7ouw
Y9UIVIeopYxI1ZgURlv+O0XZsjoAuuxerHHTocis++NGQKcpkN+6pefkKvAws6cA
lcXKdlOeAi8jH1dKFjdbXSbBpYbn8Ke/fFdrN0DNQSs5eB4HGAr1K8cXRoADh4YZ
4SBfWrFDwoJZU5foUcK22rXiH9J4NyD6MSb5oVQVrdX3RYqwfaU//CSc1afw4ok=
=PtdC
-----END PGP SIGNATURE-----