g+
g+ Communities
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  <20102011  2012  2013  2014  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014 
<== Date ==> <== Thread ==>

Subject: Re: epics debian repository update
From: Bill Lavender <lavender@agni.phys.iit.edu>
To: tech-talk@aps.anl.gov
Date: Wed, 19 May 2010 15:25:14 -0500
On Wed, May 19, 2010 at 02:36:58PM -0500, Andrew Johnson wrote:
> 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.

Official Debian packages never, ever go in /opt.  /usr/lib/epics might work.
For example, the various Java versions live in /usr/lib/jvm.  But you would
still be expected to put symlinks, or wrapper scripts, or some such in
/usr/bin, /usr/include, /etc, ... so that user commands could still work
without /usr/lib/epics in the PATH.  The only way to know is to try to
submit it for inclusion in the Debian repositories.  Carlo Segre could
probably help you with this process.  However, for a package as big as
EPICS, be prepared to deal with month and months and months of arguments
with the Debian developers and community about how things should be done.

Bill Lavender


References:
epics debian repository update Davidsaver, Michael
Re: epics debian repository update Bill Lavender
RE: epics debian repository update Davidsaver, Michael
Re: epics debian repository update Andrew Johnson

Navigate by Date:
Prev: Re: compiling SDDS, libpng.a Robert Soliday
Next: EPICS base compiling using Visual C++ 2010 Express Carsten Winkler (HZB)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014 
Navigate by Thread:
Prev: Re: epics debian repository update Andrew Johnson
Next: RE: epics debian repository update Davidsaver, Michael
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·