From a quick glance, that looks like a sensible way to go. Will investigate further. Thanks!
From: Sean Davis [mailto:[email protected]] Sent: 13 June 2016 15:37 To: Waldman, Simon <[email protected]> Cc: Software Carpentry Discussion <[email protected]> Subject: Re: [Discuss] off-topic (?): source-controlling config files Take a look at git submodules and subtrees. Many folks end up using git submodules, but subtrees are, in some senses, simpler and often suffice. There are a number of good posts online about one versus the other. As is often the case with Git, I’d suggest trying both and see which feels more natural for your situation. Sean On Jun 8, 2016, at 12:20 PM, Waldman, Simon <[email protected]<mailto:[email protected]>> wrote: Hi all, I hope this is not too off-topic for the list, since it’s not directly about SWC; apologies if so. I’m starting to use a modelling system (written by others) where some important aspects of its configuration – relating to scientific logic rather than just build issues – are set by flags in the makefile and then conditional compilation. I’ve been thinking about how to make things sane and reproducible. My first thought was to source-control the makefile with my other model input files (I do love putting model input files into git). But, obviously, the makefile is already in the repo for the software itself. I *could* import all of the software’s source (over 100Mb) into my “model inputs” repo, which would make everything entirely traceable and reproducible, but… it seems silly, and probably not the right way to do things. Any advice would be appreciated! Thanks Simon -- Simon Waldman / [email protected]<mailto:[email protected]> PhD researcher, ICIT / Heriot-Watt University Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With campuses and students across the entire globe we span the world, delivering innovation and educational excellence in business, engineering, design and science. The contents of this e-mail (including any attachments) are confidential. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. _______________________________________________ Discuss mailing list [email protected]<mailto:[email protected]> http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
