EPICS Home

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: Best practices for introducing new dot releases of modules.
From: "Shankar, Murali" <[email protected]>
To: "[email protected]" <[email protected]>
Date: Wed, 20 Feb 2013 10:58:20 -0800

Hello all,

 

  I have a noobie EPICS build system question. What I am actually trying to do is to figure out how to introduce a new version of a module (for example, the sequencer, as it is widely used) with a minor bug fix. My users do not want me to patch in place; so I take seq-R2-0-11-lcls4  and create a new dot release of the sequencer – for example, seq-R2-0-11-lcls5. I change the IOC application to use the new version of the module. However, when I try to build it, I get

 

Definition of SNCSEQ_MODULE_VERSION conflicts with ASYN support.

In this application a RELEASE file defines

                SNCSEQ_MODULE_VERSION = seq-R2-0-11-lcls5

but ASYN at /afs/slac/g/lcls/epics/modules/R3-14-12/asyn/asyn-R4-17-RC1-lcls1 defines

                SNCSEQ_MODULE_VERSION = seq-R2-0-11-lcls4

Definition of SNCSEQ conflicts with ASYN support.

In this application a RELEASE file defines

                SNCSEQ = /afs/slac/g/lcls/epics/modules/R3-14-12/seq/seq-R2-0-11-lcls5

but ASYN at /afs/slac/g/lcls/epics/modules/R3-14-12/asyn/asyn-R4-17-RC1-lcls1 defines

                SNCSEQ = /afs/slac/g/lcls/epics/modules/R3-14-12/seq/seq-R2-0-11-lcls4

Definition of SNCSEQ conflicts with MOTOR support.

In this application a RELEASE file defines

                SNCSEQ = /afs/slac/g/lcls/epics/modules/R3-14-12/seq/seq-R2-0-11-lcls5

but MOTOR at /afs/slac/g/lcls/epics/modules/R3-14-12/motor/motor-R6-6-RC2-lcls1 defines

                SNCSEQ = /afs/slac/g/lcls/epics/modules/R3-14-12/seq/seq-R2-0-11-lcls4

 

 

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? We do maintain a shared repository of modules; so perhaps that’s the issue. Are there standard techniques people use to introduce new versions of modules?

 

Any help is appreciated.

 

Regards,

Murali

 


Replies:
RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
Re: Best practices for introducing new dot releases of modules. Ron Sluiter
RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
Re: Best practices for introducing new dot releases of modules. Andrew Johnson

Navigate by Date:
Prev: trying to compile snmp for Wiener PL512 crate application James F Ross
Next: RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
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: trying to compile snmp for Wiener PL512 crate application James F Ross
Next: RE: Best practices for introducing new dot releases of modules. Allison, Stephanie
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