EPICS Controls 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  2019  2020  2021  2022  2023  2024  <20252026  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  <20252026 
<== Date ==> <== Thread ==>

Subject: Re: Basic EPICS bootstrap (rant)
From: Ralph Lange via Tech-talk <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Wed, 8 Oct 2025 15:10:24 +0200
Well,

I do understand and share your frustration.
Here's my 2 cts.

There is no standard set of modules.
Some are used more widely, some are used less widely, but there is no standard set.
Collections like synApps usually work well for the facility where they are maintained, less well for facilities with similar age, setup and requirements. They often make little sense for facilities that are fundamentally different.
These collections are also inclusive: You will compile and deploy more than you need.

There half a dozen different solutions to your problem.
In the last few years, there were multiple workshops at EPICS Collaboration meetings (2019 ff.) about build and deployment options, solutions and frameworks.
The result, if any, is that each of the developers had specific requirements that motivated their specific approach. They're all different and all justified.
The workshop materials are available on the meeting websites. Very valuable.

There once were Debian packages.
15 years ago, NSLS-2 spearheaded an effort to maintain Debian packages for many common EPICS modules. That was a lot of effort and basically lasted until the facility switched to RHEL and the resources were withdrawn.
During a few EPICS Collaboration Meetings, the issue was discussed. There was interest, but no one wanted to commit the necessary resources.

Everyone needs to pick.
As there is no one-size-fits-all solution, every installation has to pick the approach that fits them best. Read the descriptions and motivations for the existing systems (from the EPICS meeting workshops), compare them to your list of requirements, discuss your options and make a decision.

Last not least... As long as you're not using one of the complete solutions:

Put RELEASE.local files in the right places.
This Base mechanism allows to keep the module configuration one level above the module directories. A single file keeps the configuration of all modules in your installation, without changes in any of the modules, consistency guaranteed. If you're editing configuration files in many modules, you're doing something wrong.

While this is certainly not an easy solution to your problem, I hope it might help find one.

Cheers,
~Ralph

Replies:
RE: Basic EPICS bootstrap (rant) Abdalla Ahmad via Tech-talk
References:
Basic EPICS bootstrap (rant) Graeme Winter via Tech-talk

Navigate by Date:
Prev: Re: xspress3 internal triggering issue Matthew Newville via Tech-talk
Next: RE: xspress3 internal triggering issue Keith Surrena 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  <20252026 
Navigate by Thread:
Prev: Re: Basic EPICS bootstrap (rant) Anders Lindh Olsson via Tech-talk
Next: RE: Basic EPICS bootstrap (rant) Abdalla Ahmad 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  <20252026 
ANJ, 19 Mar 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·