EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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 ==>
Subject: Re: RPM packages for EPICS
From: Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Date: Thu, 22 Apr 2021 09:55:58 +0200
On Wed, 21 Apr 2021 at 17:36, Johnson, Andrew N. via Tech-talk <tech-talk at aps.anl.gov> wrote:
On Apr 21, 2021, at 9:43 AM, Hu, Yong <yhu at bnl.gov> wrote:
>
> Has any facility built, smoothly deployed and happily used RPM packages for EPICS installation of the base and popular support modules (seq, asyn, motor, streamDevice, etc.)? Please share your repositories (or building rules / specs) and your experience. Thank you!

ITER has been building RPMs for all their software including EPICS modules on RHEL for many years, but I don’t believe they are allowed to share the results with the community for intellectual property reasons (administrative and legal, not for any technical reasons).

IP issues are just a small aspect of this...
Let me iterate (we have been presenting this at collaboration meetings).

The ITER controls division builds and distributes CODAC Core System (CCS), a RHEL based Linux distribution for all control system developments in the context of the ITER project. All CCS software is packaged as RPMs.

However, all CCS software modules are built using Maven. RPM packaging is done "under the hood" by a proprietary Maven ITER plugin, as a part of Maven's "package" goal, using the results of the Maven "compile" goal. Most CCS RPMs do not install in the standard RHEL system locations, but into a structure below '/opt/codac', the EPICS parts keeping the original non-standard directory structure.

If you are linked to the ITER project, you can register to become a CODAC Core System user and use the complete ecosystem.
Installing CCS RPMs on a standard RHEL system is technically possible, but as they are not generated in a standard way, do not follow all applicable Fedora / Red Hat guidelines, install in non-standard locations and often require other CCS packages, they are of very limited use outside CCS.

Cheers,
~Ralph
Replies:
Re: RPM packages for EPICS Michael Davidsaver via Tech-talk
References:
RPM packages for EPICS Hu, Yong via Tech-talk
Re: RPM packages for EPICS Johnson, Andrew N. via Tech-talk
Navigate by Date:
Prev: How to get the Time format (H:M:S) in scalcout? Tasaddaq Khan via Tech-talk
Next: Re: What is the best (and simple) way to implement security in a Phoebus solution? Oscar Ibañez 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  2019  2020  <2021>  2022  2023  2024 
Navigate by Thread:
Prev: Re: RPM packages for EPICS Johnson, Andrew N. via Tech-talk
Next: Re: RPM packages for EPICS Michael Davidsaver 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  2019  2020  <2021>  2022  2023  2024 
ANJ, 22 Apr 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·