Date: Fri, 15 Mar 2002 16:13:35 -0500
From: Pete Fritchman <petef@databits.net>
To: Ernst de Haan <znerd@FreeBSD.org>
Cc: ports@FreeBSD.org
Subject: Re: Storing a C file in ${FILESDIR} ?
Message-ID: <20020315161335.A8629@databits.net>
In-Reply-To: <200203151938.UAA10966@smtp.hccnet.nl>; from znerd@FreeBSD.org on Fri, Mar 15, 2002 at 08:37:43PM %2B0100
References: <200203151938.UAA10966@smtp.hccnet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
++ 15/03/02 20:37 +0100 - Ernst de Haan:
| Hi,
|
| Is it okay to store one small .c file in ${FILESDIR} ? At the moment my
| www/orion port uses an 'orionctl' script for starting and stopping the
| daemon. But I would like 'orionctl' to be available for all users in the
| group 'www'. Since chmod +s is disabled for shell scripts, I'm going to write
| a small C file.
|
| Somehow it doesn't `feel' right if I put it in ${FILESDIR}. But it's very
| small, so.... I don't really know. Couldn't find anything in the Porters
| Handbook about this.
|
| Any comments?
locate .c | grep /usr/ports | grep files | grep -v "files/patch-"
Lots of ports do it, I'd say it would be fine.
--pete
--
Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)]
finger petef@databits.net for PGP key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020315161335.A8629>