On 2/27/13 6:43 PM, Mark Rivers wrote:
> I don't know how to make that process better, but copying and reconciling the CONFIG_SITE files between EPICS releases is one of the most tedious and error prone parts of upgrading EPICS base.
Hi, Mark.
I agree that this is a pain. What I do is keep track of exactly what
changes I make to configure files (all files, actually). This list of
changes can be as simple as a diff. For an upgrade, I check each change
and see if it's necessary in the new version.
Another possible approach might be something like OpenBSD's sysmerge
tool [1]. It helps perform the task of updating configuration files
after an upgrade by walking through differences and offering a chance to
merge. EPICS Base could provide something similar, maybe called
"epicscfgmerge", to work on EPICS configuration files.
Lewis
1. Search for "sysmerge" at <http://www.openbsd.org/cgi-bin/man.cgi>
- References:
- Problem building EPICS 3.14.12.3 on Cygwin Mark Rivers
- Re: Problem building EPICS 3.14.12.3 on Cygwin Andrew Johnson
- RE: Problem building EPICS 3.14.12.3 on Cygwin Mark Rivers
- Navigate by Date:
- Prev:
Re: Strange Interaction between CA gateway and CAJ Eric Norum
- Next:
areaDetector R1-9 released Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Problem building EPICS 3.14.12.3 on Cygwin Mark Rivers
- Next:
Get /usr/lib/libXm.a error while building MEDM Yasemin Barutçu
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|