EPICS RE: RELEASE file

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 <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 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024
<== Date ==>		<== Thread ==>

Hi Keenan,

Now that you have added these lines to configure/RELEASE in those modules:

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

I would suggest that you now remove these lines:

-include $(TOP)/../configure/SUPPORT.$(EPICS_HOST_ARCH)

-include $(TOP)/../configure/EPICS_BASE.$(EPICS_HOST_ARCH)

Those lines were present to allow overriding the definitions of EPICS_BASE and SUPPORT, for example when building Windows in the same tree as Linux.

But these lines are no longer needed because $(TOP)/../RELEASE.$(EPICS_HOST_ARCH).local can override both EPICS_BASE and SUPPORT.

I will fix the modules I am responsible for.

Mark

From: [email protected] <[email protected]> On Behalf Of Lang, Keenan C. via Tech-talk
Sent: Tuesday, June 11, 2019 2:48 PM
To: Florian Feldbauer <[email protected]>; [email protected]
Subject: Re: RELEASE file

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

alive

autosave

busy

calc

caputRecorder

delaygen

love

lua

motor

optics

softGlue

softGlueZynq

sscan

std

vac

vme

Yokogawa_DAS

From: [email protected] <[email protected]> on behalf of Florian Feldbauer via Tech-talk <[email protected]>
Sent: Tuesday, June 11, 2019 2:39:27 AM
To: [email protected]
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

Subject:	RE: RELEASE file
From:	Mark Rivers via Tech-talk <[email protected]>
To:	"'Lang, Keenan C.'" <[email protected]>, Florian Feldbauer <[email protected]>
Cc:	tech-talk <[email protected]>
Date:	Sun, 29 Sep 2019 18:41:08 +0000

Experimental Physics and Industrial Control System