hi
I would like some advices on good practices
On our site we used to have only one EPICS base with supports linked on.
The goal is to install few EPICS releases on site with a smart approach. The goal is at the end, to containerise(?) each application.
The following command line in the RELEASE file could free
EPICS_BASE:=$(shell echo ${EPICS_BASE})
With a shell script at the TOP of the base which can set automaticaly user environment with a generic command like this :
EPICS_BASE=${BASH_SOURCE##*/}
User’s application (environment) could be configured on the same way using the good generic script shell under the EPICS base directory the developper want to choose.
This generic approach sounds very smart, BUT, at the end, we can not really know on which EPICS_BASE an application was linked if the information is not stored elsewhere. CHECK_RELEASE is not smart enough to check that.
I’m very divided on this issue
Did any body try this approach?
Are there any EPICS container experiences?
Any others suggestions?
Thanks
En télétravail le jeudi
No téléphone : 02 31 45 46 56
________________________________________________________
Je vous encourage à m'inviter aux réunions directement sous Outlook.
________________________________________________________
Il n'y a d'histoire digne d'attention que celle des peuples libres. L'histoire des peuples soumis au despotisme n'est qu'un recueil d'anecdotes.
Sébastien-Roch Nicolas De Chamfort