Experimental Physics and
Industrial Control System

Hello, EPICS Base developers!

Why do the scripts in the EPICS Base 3.14, 3.15, and 3.16 startup
directory refer to things that are not dependencies of EPICS
Base (e.g., EPICS_EXTENSIONS, PSPRINTER for some extensions,
EPICS_DISPLAY_PATH and BROWSER for MEDM, ADTHOME for ADT, Exceed X11,
etc.)?

IMO, the startup scripts should only refer to things related to EPICS
Base.  For example, EPICS Base doesn't know anything about MEDM nor
should it.  Therefore, <EPICS Base>/startup/Site.profile should not
set EPICS_DISPLAY_PATH or anything else that relates to MEDM.  A much
better way would be for the EPICS Extensions package (currently known
as "Extensions build configure files") to provide a Site.profile, for
example, that can be edited to provide the environment or shell changes
required by the different extensions.  Since MEDM, for example, is
an extension, then EPICS_DISPLAY_PATH and BROWSER should be set in
the Site.profile provided with the EPICS Extensions package, not the
Site.profile in EPICS Base.

Thanks,

Lewis

Replies:

Re: Why do EPICS Base startup scripts refer to non-depedencies? Andrew Johnson

Navigate by Date:

Prev: Re: Inconsistent EPICS Base 3.14 startup files J. Lewis Muir

Next: Re: Why do EPICS Base startup scripts refer to non-depedencies? Andrew Johnson

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: Inconsistent EPICS Base 3.14 startup files J. Lewis Muir

Next: Re: Why do EPICS Base startup scripts refer to non-depedencies? Andrew Johnson

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