P
Peter Pk
Given there may be a complex task -
ie: spawns a shell process running "make", "vcbuild", "ant" or
whatever
or invokes a large ruby subroutine
Given that the module is opaque to ruby and needs to be invoked to
determine whether it does or does not need to rebuild it's (file)
target. How might one have the dependent task invoke this check in this
ancestor during the traversing of the dependencies, and if the ancestor
task decides it is "up to date" *not* execute it's block, triggering all
it's dependents to rebuild.
Something like overriding an "is_up_to_date" method on a file task which
is invoked during checking the graph of dependencies?
ie: inside ancestor
def is_up_to_date
sh "checkAndMaybeBuildIt ..." # may or may not build it's targets
return(no_targets_updated)
end
and if this task may or may not update multiple target files?
(should I get the Rake source code? How to get it? via Gems?)
???
ie: spawns a shell process running "make", "vcbuild", "ant" or
whatever
or invokes a large ruby subroutine
Given that the module is opaque to ruby and needs to be invoked to
determine whether it does or does not need to rebuild it's (file)
target. How might one have the dependent task invoke this check in this
ancestor during the traversing of the dependencies, and if the ancestor
task decides it is "up to date" *not* execute it's block, triggering all
it's dependents to rebuild.
Something like overriding an "is_up_to_date" method on a file task which
is invoked during checking the graph of dependencies?
ie: inside ancestor
def is_up_to_date
sh "checkAndMaybeBuildIt ..." # may or may not build it's targets
return(no_targets_updated)
end
and if this task may or may not update multiple target files?
(should I get the Rake source code? How to get it? via Gems?)
???