Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First cut at createRemakefile() function.
createRemakefile()
in USGS-VIZLAB/example, it's [mostly] possible to runremake::make(remake_file='remake.yaml')
and build the entire example project! That makes for a good start on Switch to remake? #246.remake::make(remake_file='remake.yaml')
in a fresh session, things break unless I manually source those files listed insources:
. Why would this be? I don't understand.make
the provenance of resources from vizlab #215 (but are these resources now getting copied over twice, once byremake
and once byvizlab
? more inspection & testing needed here, too)fetch
- just callsfetch
on every item.fetch
,process
, etc. individuallyHere's the remake.yaml that gets built for USGS-VIZLAB/example using this PR: