On Nov 4, 2016, at 8:20 AM, Ralph Lange <[email protected]> wrote:
> When changing towards a more typical setup, please have a look at the *.local override mechanism that is used more and more widely.
> E.g.: The standard $TOP/configure/RELEASE includes (at the end of the file) $TOP/../RELEASE.local and $TOP/configure/RELEASE.local
Should I add the necessary -include statements for these to the RELEASE and CONFIG_SITE files in the makeBaseApp template?
Yes, why not.
It's true that the templates will be used primarily for applications (i.e. local things) and the .local mechanism is more targeted to modules that are in a public repository and shared between developers with different environments and setups. (The setup
will most likely be the same at one installation.)
But to show people a suggestion of how to do that, improve uniformity, since configuring a bunch of modules using one file might be useful even for a local application, and since it doesn't do any harm when the .local files don't exist, sure.
Should I include a .gitignore (and .hgignore, .cvsignore etc.) files in the templates as well while I'm at it?
No. Choosing a VCS and configuring it should be left to the user. Each installation typically has a common ignore file for all modules, and the *.local pattern should be added there.