EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023 
<== Date ==> <== Thread ==>
Subject: Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12)
From: Ralph Lange <[email protected]>
To: "Johnson, Andrew N." <[email protected]>
Cc: EPICS core-talk <[email protected]>
Date: Fri, 4 Nov 2016 19:59:47 +0100
Hi Andrew,

On Fri, Nov 4, 2016 at 4:28 PM, Johnson, Andrew N. <[email protected]> wrote:
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.
 
Thanks for that suggestion!
~Ralph

Replies:
Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Torsten Bögershausen
References:
Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Johnson, Andrew N.
Navigate by Date:
Prev: Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Johnson, Andrew N.
Next: Jenkins build is back to stable : epics-base-3.14-win32s #159 APS Jenkins
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023 
Navigate by Thread:
Prev: Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Johnson, Andrew N.
Next: Re: [epics-modules/iocStats] Move MODULE_SITE_TOP definition to the end of the file (#12) Torsten Bögershausen
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023 
ANJ, 06 Nov 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·