This is another in a long line of Project directory organization questions of mine. I'm trying to build a project directory organization structure which follows best-practices. I'd like the structure to be set up in a way that is easy to deliver to others and have them execute it. Adapting this structure, part of my project structure would look as follows:
common-data/ LocalTexTree/ projects/myproject/ projects/myproject/myproject.exe projects/myproject/code/r/main.r projects/myproject/data/myproject-data.dat projects/myproject/report/main.tex
Q: Suppose I'd like to deliver my full project to someone for execution using
myproject.exe. What's the best way to do that?
My concern is that
LocalTexTree will be large and have a lot of files irrelevant to "myproject". From reading around, I suspect the solution would be to track the relevant files in a Makefile(?) that zips the entire project. That just seems like too clunky a solution and that it would break easily. There has to be a better way, right?
Again, I'm no programmer. This stuff isn't obvious to me at all. Any and all comments are welcome!