https://bugzilla.redhat.com/show_bug.cgi?id=979124
--- Comment #70 from Erik Schilling <ablu.erikschilling(a)googlemail.com> ---
@Windows/OS X modules:
Na I do not think it makes any sense to include them... They are useless on
linux. So if I would do a subpackage (qbs-wix for eg.) for them it would be a
useless confusing package. If I would stick it into the main package it bloats
that package for no good. I am trying to keep qbs as modulizable as it is
provided.
Also you said that modules are fine to be removed :P
Though I am of course open for further discussions ;) In case you (upstream)
somewhen plan to introduce modules which cannot be removed easily (what I do
not hope). I would need to reconsider this...
@autotests:
Well it _is_ possible to run the tests, but since I seem to be the only one who
runs the tests in such a setup I always hit issues when you do changes
upstream. For example my old setup stopped working due to some changes and
understanding why it stopped working + then opening a bugreport about it (or do
countless builds to test it on my end) is a bit annoying for me at the moment.
Maybe I can setup a continuos integration which builds my package with each
changeset you do would help me to catch those issues before release time... But
I would need to setup this...
So: I would like to run the tests myself too, I just need to find a good
maintainable way to do this.
Regards,
Erik
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component