File conflicts with qtscriptgenerator

• Nov 9, 2010 - 23:36

As a packager of musescore for Arch Linux I was notified that there
are file conflicts between the Arch Linux package for
qtscriptgenerator, which is required by by a popular application like
amarok. That means if I follow the easiest approch and add a conflict,
users would have to decide if they want to use musescore or amarok.

The conflicting files are:

/usr/lib/qt/plugins/script/libqtscript_core.so
/usr/lib/qt/plugins/script/libqtscript_gui.so
/usr/lib/qt/plugins/script/libqtscript_network.so
/usr/lib/qt/plugins/script/libqtscript_uitools.so
/usr/lib/qt/plugins/script/libqtscript_xml.so

Is there a better way to handle this? For instance

1. Can I simply remove these files and let musescore depend on
qtscriptgenerator?

2. Can I easily change the build process in a way that the files are
stored under a different name?

3. Other suggestions?

I asked the same question in another thread but was asked to open a new thread for this.

Comments

[DELETED] 5

• Nov 10, 2010 - 10:27

By file conflict I guess you mean that MuseScore wants to install the same file at the same place right?
If it's the case, MuseScore can use the same files than Amarok. On other distribution such as Fedora, there is a special package (named QtScriptbindings I think) and MuseScore package depends on it. So you don't need to compile the scriptgen directory, just add a dependency on this package. Does it make sense?

You can catch me on IRC : #musescore on freenode.net

haawda

• Nov 10, 2010 - 18:20

> By file conflict I guess you mean that MuseScore wants to install the same file at the same place right?

exactly

> On other distribution such as Fedora, there is a special package (named QtScriptbindings I think) and MuseScore
> package depends on it.

also in Arch Linux

>...just add a dependency on this package. Does it make sense?

Completely.. Thank you.