Re: RELEASE file

[Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov>]

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 <tech-talk-bounces@aps.anl.gov> on behalf of Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov>
Sent: Tuesday, June 11, 2019 2:39:27 AM
To: 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