Soliciting opinions on #137993

[Fergal Daly]

Saying that I must install a browser to install mplayer-plugin is like
saying you I must install an MP3 player to install an mp3 library.

I spotted an argument that it won't be uninstalled when the last
browser is uninstalled. How is that handled for libraries?

F

2008/5/16 Forest Bond <forest at alittletooquiet.net>:
> Hi,
>
> Please review the ticket:
>
> https://bugs.launchpad.net/ubuntu/+source/mplayerplug-in/+bug/137993
>
> The question is whether or not the mplayerplug-in package should Depend on each
> and every browser package that supports it.  The problem with this approach, of
> course, is that if one such browser is missed (and new browsers *do* get
> introduced in releases), then the user has to install a browser he doesn't
> intend to use.
>
> In my opinion, the ideal situation is for all Gecko-based browsers to Provide
> gecko-browser so that plugin packages can depend on that.  However, this is not
> currently in place.  Given that, I'd prefer it if plugin packages downgrade this
> dependency to Recommends.
>
> Opinions?
>
> Thanks,
> Forest
> --
> Forest Bond
> http://www.alittletooquiet.net
> http://www.pytagsfs.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFILapaRO4fQQdv5AwRApruAJ9HCbvIGZ13P7pKCswU7/D4CgqMzwCfS677
> UnE2rSFthRkV5vobhlSFv7c=
> =OPoA
> -----END PGP SIGNATURE-----
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
>