EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Best practices for introducing new dot releases of modules.
From: Andrew Johnson <[email protected]>
To: [email protected]
Cc: "Shankar, Murali" <[email protected]>
Date: Wed, 20 Feb 2013 13:57:53 -0600
Hi Murali,

On 2013-02-20 Shankar, Murali wrote:
> So, to test a dot release of the sequencer, should I rebuild all the other
> modules that the app depends on that also depend on the sequencer?

Yup, that's what you have to do to solve this properly.  Although the new 
version could be fully compatible with the old one, there is no way for the 
build system to test that compatibility, so by default it enforces the safest 
option, which is to not allow the build to continue.  I added the module 
checking mechanism because in the past linking incompatible modules together 
has caused numerous some really strange and often extremely subtle bugs to 
turn up here at APS, in some cases only being noticed days or even weeks after 
we booted the IOC.

If you as the author of the IOC are certain that the changes did not involve 
modifying any struct or class definitions, or changing any routines in an 
incompatible way you can edit your application's configure/CONFIG_SITE file 
and set CHECK_RELEASE to WARN (it also accepts NO but I don't recommend using 
that) which will then allow the build to complete despite the warnings.

- Andrew
-- 
There is no such thing as a free lunch.  When invited for lunch,
it is best to check if you are there to eat, or to be eaten.
-- Clive Robinson

Replies:
RE: Best practices for introducing new dot releases of modules. Shankar, Murali
References:
Best practices for introducing new dot releases of modules. Shankar, Murali

Navigate by Date:
Prev: RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
Next: EDM Text Control Widget Motif behavior Isadoro Carlino
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
Next: RE: Best practices for introducing new dot releases of modules. Shankar, Murali
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·