https://bugzilla.redhat.com/show_bug.cgi?id=979124
--- Comment #59 from Erik Schilling ablu.erikschilling@googlemail.com --- Would anybody mind if I would simply leave the files: DarwinGCC.qbs,darwin-tools.js,ios-gcc.qbs,msvc.js,osx-gcc.qbs
in the package? I fear that maintaining this list of files will be hard and error prune. Also they are part of qbs. So what tells me that I am not breaking the package for some people who include them (maybe for targets on other operating systems)?
@WiX - Module: Hm... That looks like a lot of work to keep this tested and maintained. There currently is no easy way to install it on fedora it seems. So I would prefer not to put that much effort into it (and each release again to test it) especially since it does not seem to be officially supported for linux.
@the ifarch thing: Qbs plugin system always tries to load the plugins from a fixed "/lib/". While that works on most systems it does not work on 64bit systems. Ideally this would be fixed by qbs being better at reading the right paths... I will open a bug for this on upstream.
And: it does harm since if i do this unconditionally it breaks non 64bit tests since it finds 2 cpp scanner plugins for example and fails the tests.
@Kevin: Well that is for the people who only think of it as qmake replacement. But in fact it grows to be more than that.
Regards and thanks a lot for the input, Erik