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  2013  2014  2015  2016  2017  2018  <20192020  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  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: RELEASE file
From: Mark Rivers via Tech-talk <tech-talk@aps.anl.gov>
To: "Lang, Keenan C." <klang@anl.gov>, Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 12 Jun 2019 11:58:52 +0000
Hi Florian,


If the goal is to not modify [module]/configure/RELEASE then what do you propose belongs in that file?  Only these lines?

-include $(TOP)/../RELEASE.local
-include $(TOP)/../RELEASE.$(EPICS_HOST_ARCH).local
-include $(TOP)/configure/RELEASE.local
It should not define EPICS_BASE, ASYN, etc?  In that case there needs to be some example for what the user needs to have in RELEASE.local, for example as commented out lines in configure/RELEASE?  In areaDetector we provide EXAMPLE_RELEASE.local to provide an example for the user to copy.


synApps provides support for "make release".  This updates both [module]/configure/RELEASE and [module]/configure/RELEASE.local.  If RELEASE defines anything then it will be modified and source/release control will flag it as such.


Mark



________________________________
From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov>
Sent: Wednesday, June 12, 2019 1:55 AM
To: Lang, Keenan C.; tech-talk@aps.anl.gov
Subject: Re: RELEASE file


Dear Keenan,


thanks for applying these changes. From your list I'm currently only using autosave and calc which brings me to the question:
How should optional dependencies be handled? For me the main purpose of the local release file is, that I do not have to modify configure/RELEASE for my environment anymore.

But e.g. in calc there is an optional dependency to sscan. So if I do not use sscan, I need to comment the definition of sscan out in configure/RELEASE. The same is true for asyn, where IPAC and SNCSEQ are optional dependencies.


Is there any guideline from the EPICS 7 developers how this should be handled in the future?


Best regards,
Florian


On 6/11/19 9:47 PM, Lang, Keenan C. wrote:

I have updated the RELEASE files of the following EPICS modules that the APS distributes:


alive

autosave

busy

calc

caputRecorder

delaygen

ip

love

lua

motor

optics

softGlue

softGlueZynq

sscan

std

vac

vme

Yokogawa_DAS



________________________________
From: tech-talk-bounces@aps.anl.gov<mailto:tech-talk-bounces@aps.anl.gov> <tech-talk-bounces@aps.anl.gov><mailto:tech-talk-bounces@aps.anl.gov> on behalf of Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov><mailto:tech-talk@aps.anl.gov>
Sent: Tuesday, June 11, 2019 2:39:27 AM
To: tech-talk@aps.anl.gov<mailto:tech-talk@aps.anl.gov>
Subject: RELEASE file

Dear all,

after the collaboration meeting last week, I would like to make the
request that all EPICS modules (e.g. asyn, stream, snmp, ....)
include the lines

 > -include $(TOP)/../RELEASE.local
 > -include $(TOP)/../RELEASE.$(EPICS_HOST_ARCH).local
 > -include $(TOP)/configure/RELEASE.local

in their configure/RELEASE file. These lines were introduced in base 7
and from my point of view this simplifies building EPICS via scripts!
Also I agree with Dirk Zimoch, who mentioned during the meeting, that
configure/RELEASE is not the best place to store dependencies to
specific versions.
In addition, such a line simplifies the collaborative work on a package
via git, as you do not need to modify configure/RELEASE for your
environment anymore. Thus creating merge/pull requests only contain
changes to source files and no longer changes to the environment
configuration. The file 'configure/RELEASE.local' should be included in
the .gitignore file, of course.

Best regards,
Florian

--
Dr. Florian Feldbauer

Ruhr-Universität Bochum
Experimentalphysik I AG
Universitätsstr. 150
Fach-Nr. 125
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de


--
Dr. Florian Feldbauer

Ruhr-Universität Bochum
Experimentalphysik I AG
Universitätsstr. 150
Fach-Nr. 125
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de

Replies:
Re: RELEASE file Florian Feldbauer via Tech-talk
References:
RELEASE file Florian Feldbauer via Tech-talk
Re: RELEASE file Lang, Keenan C. via Tech-talk
Re: RELEASE file Florian Feldbauer via Tech-talk

Navigate by Date:
Prev: Re: .opi from CSS to Phoebus Hinko Kocevar via Tech-talk
Next: Re: RELEASE file Florian Feldbauer via Tech-talk
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  <20192020 
Navigate by Thread:
Prev: Re: RELEASE file Florian Feldbauer via Tech-talk
Next: Re: RELEASE file Florian Feldbauer via Tech-talk
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  <20192020 
ANJ, 12 Jun 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·