You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the target package does some unnecessary filesystem inspection. It will recurse a directory or inspect a set of source files to collect the newest timestamp then compare that timestamp to a target to see if any of the source timestamps is newer than the target. The logic should be reworked to recurse/inspect, comparing against the target, and stop as soon as a newer source is found.
It would also be useful if the Dir, Glob, and Path functions supported supplying a timestamp as the target, rather than a file path. This would allow for comparison against arbitrary targets like container images using those functions. The existing three functions could then discover the target timestamp for comparison and just wrap functions that take a target timestamp.
PR inbound
The text was updated successfully, but these errors were encountered:
* target: rework modtime comparison logic
* fix NewestModTime, add tests for NewestModTime, OldestModTime
* added tests for Dir when target is Dir
* updates per #324
Currently, the
target
package does some unnecessary filesystem inspection. It will recurse a directory or inspect a set of source files to collect the newest timestamp then compare that timestamp to a target to see if any of the source timestamps is newer than the target. The logic should be reworked to recurse/inspect, comparing against the target, and stop as soon as a newer source is found.It would also be useful if the
Dir
,Glob
, andPath
functions supported supplying a timestamp as the target, rather than a file path. This would allow for comparison against arbitrary targets like container images using those functions. The existing three functions could then discover the target timestamp for comparison and just wrap functions that take a target timestamp.PR inbound
The text was updated successfully, but these errors were encountered: