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  2013  2014  2015  2016  <20172018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019 
<== Date ==> <== Thread ==>

Subject: Additional RELEASE file checks
From: Hugo Slepicka <hhslepicka@gmail.com>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 05 Apr 2017 23:30:46 +0000
Hi,

Here at SLAC we organize our RELEASE files with variables for the versions of the modules and after that the path for them, e.g.:

    ASYN_MODULE_VERSION=R4.30-0.3.0
    CEXP_MODULE_VERSION=R1.0.1
    STREAM_MODULE_VERSION=R2.7.7-0.1
    YAMLLOADER_VERSION=R1.0.1

    ASYN=$(EPICS_MODULES)/asyn/$(ASYN_MODULE_VERSION)
    CEXP=$(EPICS_MODULES)/cexpsh/$(CEXP_MODULE_VERSION)
    STREAM=$(EPICS_MODULES)/streamdevice/$(STREAM_MODULE_VERSION)
    YAMLLOADER=$(EPICS_MODULES)/yamlloader/$(YAMLLOADER_VERSION)

With the migration to R3.15.5 and the change on our tag naming convention we started to see the following error message:
----------------------------
This application's RELEASE file(s) define
    YAMLLOADER_VERSION = R1.0.1
after but not adjacent to
    CEXP_MODULE_VERSION = R1.0.1
both of which resolve to     /afs/slac.stanford.edu/u/lt/jvasquez/sandbox/test/BunchLengthMonitor-git/configure/O.rhel6-x86_64/R1.0.1
Module definitions that share paths must be grouped together.
Either remove a definition, or move it to a line immediately
above or below the other(s).
Any non-module definitions belong in configure/CONFIG_SITE.
----------------------------

Here are the questions:
- What would be the problem of having more than one variable pointing to the same place?

- Are the order of the includes and linking defined by the other that they appear at the RELEASE file?

We know that there are solutions such as adding the variables immediately above or below the other and also bring the version number to the module path to avoid conflicts but we are curious to understand why.

The additional checks were introduced with this commit:
https://github.com/epics-base/epics-base/commit/67097456e33cac9f33af0673c4ee5daa7fe09272#diff-62e7292bd50b6eeaec4ca166b146ba7eR243

Thank you,
Hugo

Replies:
Re: Additional RELEASE file checks Michael Davidsaver

Navigate by Date:
Prev: How to ignore ACK character in response (motor-6-9, asyn-4-30) David Vine
Next: Re: Additional RELEASE file checks Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019 
Navigate by Thread:
Prev: Re: How to ignore ACK character in response (motor-6-9, asyn-4-30) David Vine
Next: Re: Additional RELEASE file checks Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019