Date: Wed, 4 Dec 1996 19:45:54 -0800 From: obrien@NUXI.com (David E. O'Brien) To: CVS-committers@freefall.freebsd.org, ports@freebsd.org Subject: Re: news/lib - lib/news ??? Message-ID: <Mutt.19961204194554.obrien@relay.nuxi.com> In-Reply-To: <Pine.BSF.3.95.961205025426.1538A-100000@nagual.ru>; from ????????????????????????????? on Dec 5, 1996 02:58:18 %2B0300 References: <199612042242.WAA07173@veda.is> <Pine.BSF.3.95.961205025426.1538A-100000@nagual.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> > $ ls -lR /usr/local/libexec/news
> > total 492
> > drwxr-xr-x 2 bin bin 512 Sep 29 1994 batch/
> > -rwxr-xr-x 1 bin bin 30414 May 10 1996 canonhdr*
> > -rw-r--r-- 1 bin bin 858 May 25 1995 canonsys.awk
>
> I thik most of this stuff belongs to /usr/local/lib/news
> (in agreement with tradition)
> news/bin maps directly to bin and few daemons goes to sbin...
> I think we ever don't need libexec or etc in that scheme...
I totally disagree. The "Subdirectories" subsection of the portint
section of the handbook states:
${PREFIX}. Some ports lump everything and put it in the subdirectory
with the port's name, which is incorrect. Also, many ports put
everything except binaries, header files and manual pages in the a
subdirectory of `lib', which does not bode well with the BSD paradigm.
Many of the files should me moved to one of the following: `etc'
(setup/configuration files), `libexec' (executables started
internally), `sbin' (executables for superusers/managers) or `share'
(architecture independent files). See hier(7) for details, the rule
governing /usr pretty much applies to /usr/local too.
So our rule is libexec should be used. If not, then lets update the
handbook.
--
-- David (obrien@cs.ucdavis.edu)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19961204194554.obrien>