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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: EPICS release series after 7.0: 7.1 or 8.0? (ABI) |
From: | "Johnson, Andrew N. via Tech-talk" <[email protected]> |
To: | "J. Lewis Muir" <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Thu, 9 Jan 2020 22:50:59 +0000 |
I suggest you take a look at Sumo from HZB (BESSY-2), it's the closest equivalent to automated package management for EPICS that I've come across, but it installs everything from source. Once it has a database of your support modules, you just have to give each IOC a configure/MODULES file, which tells Sumo what support modules and versions the IOC needs. Then it can download, patch if necessary, configure and build them all from source, and configure the IOC's configure/RELEASE file, all in a single command. If any subset of those modules have already been built with the same set of upstream dependencies it will reuse those and only build the extra modules that are needed.Whenever I upgrade, I spend a fair amount of time downloading all the distribution files, patching, and getting everything to build correctly. I wish to have binary packages that I could build once and then install on Linux and macOS machines. I was thinking of using pkgsrc so that I could use one package management system to build and install binary packages for a number of platforms including Linux and macOS. Then, for example, it would be as simple as "pkgin install epics" to install EPICS on a machine.
-- Complexity comes for free, Simplicity you have to work for.