FS#18110 - [miro] does really depend on xine-lib?
Attached to Project:
Arch Linux
Opened by Giulio Fidente (giulivo) - Monday, 01 February 2010, 19:47 GMT
Last edited by Jan de Groot (JGC) - Thursday, 15 April 2010, 09:34 GMT
Opened by Giulio Fidente (giulivo) - Monday, 01 February 2010, 19:47 GMT
Last edited by Jan de Groot (JGC) - Thursday, 15 April 2010, 09:34 GMT
|
Details
Description:
Once installed, miro can be configured to use xine OR gstreamer as backend ... but we have xine-lib listed as dependency, wouldn't it be better to have it listed as suggestion instead of forcing users to install xine-lib (and few others) as dependency even if not used? Additional info: * package version(s) - 2.5.4-2 |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 15 April 2010, 09:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Not a bug anymore: miro has been updated to 3.0, there's no xine backend there anymore.
Thursday, 15 April 2010, 09:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Not a bug anymore: miro has been updated to 3.0, there's no xine backend there anymore.
FS#14684, not sure if it is still the case but I presume it is as it is just one minor release ago.As per
FS#14684you had gstreamer in the optional packages, while it is the default, I'm just wondering why we don't move xine-lib in the optionals, considering that it is not needed to run miro (nor to have playback functionalities that gstreamer delivers)gstreamer0.10-good-plugins 97
+ gstreamer0.10-ugly-plugins 108
+ gstreamer0.10-bad-plugins 150
In terms of dependencies, xine-lib is more feasible than the gst framework ... but Miro depends on GNOME, which in turns would install a lot of those gstreamer dependencies; unfortunately I don't have any clean GNOME installation to check how much those numbers would change, I'm just assuming that a GNOME user will probably have gstreamer0.10-good-plugins already installed, but this is just _my_ (and possibly wrong) assumption.
The last option which would avoid to people using gstreamer to install xine-lib (and its dependencies) is to have them both listed as optionals but that would break somewhat a "core functionality", unless the user choose and install manually one or another backend.
I would still personally prefer to have gstreamer plugins in by default and xine-lib as opt, but at this point that's only my opinion.
Thanks for listening anyway.
and xine-lib OR xine-ui is not listed