https://bugzilla.rpmfusion.org/show_bug.cgi?id=7470
--- Comment #3 from Nicolas Chauvet <[email protected]> ---
(In reply to Bradan Fleming from comment #2)
You will need to provide two separate review request, indeed.
As I understand the makemkvcon binary (from makemkv-bin) uses the makemkv-oss
libraries. (libdriveio and libmakemkv). Then libmmbd and makemkv(gui) uses the
makemvkcon.
In any cases, both will need to be provided under the rpmfusion nonfree
repository because they are interdependent. Also all in all circle dependencies
can be dealt properly with RPM as soon as both packages version are provided at
the same time.
I would suggest the following:
-> I'm assuming that makekvcon can be used as a standalone cli tool:
- makemkv-oss having a libmakemkv and libdriveio sub-packages (or makemkv-libs
and related -devel), then have a makemkv "main" package that provides the
makemkv gui (with appdata files, and etc), and requires makemkv-bin (and
recommends makemkv-blues)
- makemkv-bin (having makemkvcon) and Requires makemkv-libs and another
makemkv-blues sub-package for the java content.
Dependency can be sorted as:
makemkv -> makemkv-bin -> makemkv-libs
For the blues, I'm not sure if it's really relevant to provides the java in the
system java classpath directory. Having it in a sub-package if optional looks a
good idea. I would just mention in the %files section which license is which
content. Although I haven't seen the sourcecode of the java content...
If the makemkvcon cannot really be used on cli, then this can probably be
simplified a little. (merging back the makemkv-libs into the main makemkv
package).
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
rpmfusion-developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
