Emmanuel Mayssat wrote:
Another question about software upgrade...
Let's say that I change the name of PV in my epics database.
Potentially with this change, I could break epics extensions.
Medm of course, but also feedback system, PV backup, etc.
Is there a way to know which extensions will break if I change a PV
name?
maybe this is nitpicking, but I had a problem reading this
email because it doesn't "break extensions". They'll still
compile and all that. What it does break is the proper working
of your particular incarnations. If you implement those
with variable substitutions they won't break - unless you
run into a similar problem that we have with some of our
dm screens:
The database (in capfast) contains records (what breaks
is the mbbis and mbbos) that have certain fields, and
certain numbers of those. If you then overload those with
pvload and dm screen that was running from before will have
the names (and numbers of items) in the database rather than
those that were loaded with pvload afterwards. Any dm
(replace by your favorite display package) screen that is
run up later with have the ones that were pvloaded and are
actually present in the database at the time.
I still wouldn't consider that 'breaking extensions'.
Aloha,
Maren
- References:
- PV name changes and epics extensions Emmanuel Mayssat
- Navigate by Date:
- Prev:
Re: PV name changes and epics extensions Don Dohan
- Next:
Re: Network plug and play epics devices Pete Jemian
- 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: PV name changes and epics extensions Rock, Judith E.
- Next:
Programmers position (again) LYNCH, Damien
- 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
|