Installation paths updates

[Georg Rudoy]

Hi there,

I've moved QML files installation paths for Vrooby from resources
(where nothing is installed on disk separately from the binary) to
$PREFIX/share/leechcraft/qml{,5}/vrooby. Don't forget to add new paths
to your packages.

Also, all QML-installing plugins now also install QML files to
$PREFIX/share/leechcraft/qml5 (notice the '5' at the end of the path).
There, Qt5-compatible QMLs are stored. Feel free to ignore this
directory if Qt5-enabled builds aren't shipped.

--
Georg Rudoy

[Dmitriy Perlow]

Georg Rudoy <0xd34...@gmail.com> Thu, 28 Aug 2014 00:16:06 +0300:

Imho Qt5 build' files shouldn't be installed if Qt4 is used because you
get file conflicts between different builds or make packagers resolve them
by files purging.

--
Best regards,
Dmitriy DA(P).DarkneSS Perlow @ Linux x64

[Georg Rudoy]

2014-08-28 8:07 GMT+04:00 Dmitriy Perlow <d...@open.by>:
> Imho Qt5 build' files shouldn't be installed if Qt4 is used because you get
> file conflicts between different builds or make packagers resolve them by
> files purging.

How do you get them? Qt4-related set of file is installed into
$PREFIX/leechcraft/qml, Qt5 — into $PREFIX/leechcraft/qml5.

--
Georg Rudoy

[Dmitriy Perlow]

Georg Rudoy <0xd34...@gmail.com> Thu, 28 Aug 2014 07:19:27 +0300:

When Qt4' build is made maintainer will have to purge Qt5 stuff from
packages not to conflict with Qt5' build, will not he or she?

[Georg Rudoy]

Yes, this is true. I haven't thought of such cases.

Anyway, perhaps it's easier to avoid packaging these files on the
package manager level (by merely ignoring a subtree during packaging)
than introduce a bunch of repetitious code in LC build system.

--
Georg Rudoy