Date: Mon, 26 Dec 2005 00:57:29 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Florent Thoumie <flz@xbsd.org> Cc: Ion-Mihai Tetcu <itetcu@people.tecnik93.com>, freebsd-stable@freebsd.org, Jose M Rodriguez <josemi@freebsd.jazztel.es>, freebsd-ports@freebsd.org Subject: Re: HEADS UP: MFC of local_startup changes to rc.d complete Message-ID: <43AFB079.2020604@FreeBSD.org> In-Reply-To: <200512231928.21444.flz@xbsd.org> References: <43A910F8.5090009@FreeBSD.org> <200512231538.21356.flz@xbsd.org> <20051223195207.6f2e6148@it.buh.tecnik93.com> <200512231928.21444.flz@xbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Florent Thoumie wrote:
> rcNG was the word for "using rc.subr".
rcNG stands for rc Next Generation. It's not the next generation anymore.
> Using the .sh extension prevents from conflicts in ${WRKDIR} and you know
> what kind of file it is in ${FILESDIR}. Anyway, what is the difference
> between adding .sh suffix in some cases and removing it in some cases ?
>
As I mentioned in one of my messages, we can easily fix this by changing
bsd.port.mk to take file.in and output $WRKDIR/file.out. I haven't finished
the patch to bsd.port.mk yet, but it's a trivial change.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43AFB079.2020604>