Something like rerunOnFileChange is a nice idea. I would suggest it should
be able to monitor folder too.
By the way, I could provide another use-case.
For example, if a user downloads a library from the Internet in a way like
qpm/npm. (Remarks. qpm does not support QBS now. I am talking about a
I could just as well ask you to provide a use case for why is it necessary
to update the Rule artifacts that don't need updating (according to QBS).
Yet alwaysRun still exists.
As for Probes: getting the git tag and commit is certainly possible by
attaching to a HEAD file in the repo,
but this is
On 10/17/2017 02:55 PM, NIkolai Marchenko wrote:
Both run arbitary scripts to do their work. QBS cannot assume that one
script is better or more expensive than the other since both are
arbitary and external to build system. So why defend the policy of not
allowing alwaysSrun for Probes ? This
Both run arbitary scripts to do their work. QBS cannot assume that one
script is better or more expensive than the other since both are arbitary
and external to build system. So why defend the policy of not allowing
alwaysSrun for Probes ? This makes no sense to me
