Titus and Dan, It doesn't seem to me to be so much a lesson on make and how it works as a lesson on how to use make for a particular purpose. That's fine and a useful thing to do, but I think that someone who might anticipate learning the basics of make might expect something different. Perhaps calling it something like "Using make to manage a manuscript" or "Using make to manage a workflow" might be both more informative and more accurate?
I might also be suspicious of the real reproducibility of something that curls a dependency (reveal.js). I would include the file 2.6.2.tar.gz renamed as reveal.js-2.6.2.tar.gz with a note of the checksum, date downloaded, and originating URL. That's just me, though. I don't trust the interwebs very much. ;-) This is a useful and nice example of using make to manage something other than the traditional compile/link process. What would you think of the idea of having a 'draft' rule that would double-line-space the text for editorial review? (Or is that now a fully deprecated method?) That would provide an opportunity to show off some more of make's capability, and it might even be useful. Thanks, -- bennet On Thu, Sep 4, 2014 at 9:28 AM, C. Titus Brown <[email protected]> wrote: > Hi all, > > Daniel Standage (not (yet) a trained SWC instructor) asked me for some > feedback on a ‘make’ lesson — > > https://github.com/standage/2014-09-03-reproducibility/blob/master/homework.md > > — and gave me permission to forward it on. Looks good to me, on a skim, but > I can’t think about it much today; would love to see comments from y'all! > > best, > —titus > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
