Subject: |
Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) |
From: |
"Johnson, Andrew N." <[email protected]> |
To: |
EPICS core-talk <[email protected]> |
Date: |
Fri, 4 Nov 2016 15:28:10 +0000 |
Hi Ralph,
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
>
> That allows to keep the local overrides outside of source control (via .gitignore) and putting a .local override either local to configure a specific module or "one level up" to configure a whole bunch of modules using a single file.
Should I add the necessary -include statements for these to the RELEASE and CONFIG_SITE files in the makeBaseApp template?
Should I include a .gitignore (and .hgignore, .cvsignore etc.) files in the templates as well while I'm at it?
- Andrew
- Replies:
- Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Ralph Lange
- Navigate by Date:
- Prev:
Re: EPICS Base Release-Candidate Double Feature! Andrew Johnson
- Next:
Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Ralph Lange
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
Re: EPICS Base Release-Candidate Double Feature! Andrew Johnson
- Next:
Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Ralph Lange
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
2025
|