Date: Tue, 19 Sep 1995 02:46:53 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: paul@freebsd.org Cc: CVS-commiters@freebsd.org, cvs-etc@freebsd.org Subject: Re: cvs commit: src/etc rc sysconfig Message-ID: <199509190946.CAA00831@silvia.HIP.Berkeley.EDU> In-Reply-To: <199509181917.MAA27052@freefall.freebsd.org> (paul)
next in thread | previous in thread | raw e-mail | index | archive | help
Duh, can we at least have some DISCUSSION before we go into commit wars like this? Jordan and Paul, please stop the rash of commits IMMEDIATELY and let's talk about it, ok? * paul 95/09/18 12:17:15 * * Modified: etc rc sysconfig * Log: * Removed startup code for pcnfsd and apache. These don't even exist * in FreeBSD and should never have got in here. I won't comment on this for now.... * Removed hard-coded /etc/rc.local.d hacks and implemented a more flexible * solution. * * Added a local configuration area to sysconfig. Objection, you used "/usr/local/etc" as the default of startup directory name, which means every file with a name that matches *.sh will be executed at startup. This is not desirable, as /usr/local/etc is a place to hold configuration scripts in general, not only ones that are executed on startup. This should at least be changed to "/usr/local/etc/rc.d" or some such. I got a new commit message now...so Jordan has now changed it to "/usr/local/etc/rc.local.d"...gosh, this is ugly, if you ask me. :< Anyway, I have a huge problem with all this stuff going into /usr/local, as there is nothing the X ports (which use PREFIX=/usr/X11R6 by default) can do to know where that tree is, as the user may have decided to put the "local" (non-X) ports into /opt or some such. This was my objection to Paul's original proposal, and the reason why nothing was implemented following the previous discussion in "ports" was that nobody could come up with a clean solution to this. Also, I dislike the idea of the string "/usr/local" now defined in two places (/etc/sysconfig and /usr/share/mk/bsd.port.mk), there should be exactly one place on the system that the user can change if we are to allow him to change it. Another thing, I would like you (and I mean both of you) to at least consult me before making such changes, as a change like this affects the whole ports paradigm. I don't want to sound too authoritative but I'm the ports manager and I would like to be at least contacted about stuff like this. Ok? :) Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509190946.CAA00831>