On Wednesday 19 May 2010 13:55:26 Davidsaver, Michael wrote:
>
> I wonder if relocating the tree under '/usr/lib/epics/' (like
> /usr/lib/gcc/) or '/opt/epics' would be more acceptable? Though I would
> definitely say that the long term solution is making the EPICS build
> system more flexible with respect to filesystem layout.
The FHS suggests /opt/epics/<package> as the best location (although I admit
that epics is not currently a LANANA registered provider name). See
http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES
for what it says about /opt. That is where I usually install the code for
training courses.
The FHS document also says:
Large software packages must not use a direct subdirectory under the
/usr hierarchy.
About /usr/lib it says:
/usr/lib includes object files, libraries, and internal binaries that
are not intended to be executed directly by users or shell scripts.
this /usr/lib/epics would not be appropriate for many things.
--
The best FOSS code is written to be read by other humans -- Harald Welte
- Replies:
- Re: epics debian repository update Bill Lavender
- References:
- epics debian repository update Davidsaver, Michael
- Re: epics debian repository update Bill Lavender
- RE: epics debian repository update Davidsaver, Michael
- Navigate by Date:
- Prev:
Re: epics debian repository update Benjamin Franksen
- Next:
Re: epics debian repository update J. Lewis Muir
- 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: epics debian repository update Benjamin Franksen
- Next:
Re: epics debian repository update Bill Lavender
- 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
|