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 way to implement it by using QBS itself) In using this method, the library dependency is not managed by the user themselves. User expects the newly downloaded library should be added to their build system after running the command. An auto re-run Probe item should help to implement such kind of system. On 17 October 2017 at 21:45, NIkolai Marchenko <[email protected]> wrote: > 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 completely counterintuitive and getting a tag and commit very > certainly is not an > "expensive operation that takes time". Why not simply let us set alwaysRun > and take responsibility for this running each time? > > Or, if you think it more sensible, provide an option for the probe > rerunOnFileChange: [list of files] > which is what people are doing at the moment anyway so you might as well > make it officialy supported function > > On Tue, Oct 17, 2017 at 4:33 PM, Joerg Bornemann <[email protected]> > wrote: > >> 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 makes no sense to me >>> >> >> Could you sketch a use case for probes that always run, please? >> >> >> Cheers, >> >> Joerg >> _______________________________________________ >> Qbs mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/qbs >> > > > _______________________________________________ > Qbs mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qbs > >
_______________________________________________ Qbs mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
