[RFC][Change-Request] Create usefulness in rc.subr etc/rc.conf.d/*.conf namespace.

[Doug Barton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I agree with Gordon's analysis that this proposal adds a lot of
potential for confusion with very little real benefit. Your post
describes _what_ you want to do, but I'm confused about _why_ you would
want to do it. Can you give a use case example?

I also feel compelled to point out that if the functionality you want is
"break certain common knobs for a subset of services out into their own
configuration file" then this can already be achieved without any code
changes by placing ". /path/file" in your rc.conf[.local] file(s). You
can even put the code snippet you posted in there if you really feel
that it's the right solution. And yes, I heard you say elsewhere in the
thread that you don't like to put anything other than variables in
rc.conf, but there is nothing actually wrong with doing it, and it works.

In short, I've reviewed this whole thread to date and haven't yet seen a
compelling reason to make this change.


Doug

- -- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBCAAGBQJNyE5oAAoJEFzGhvEaGryEEgkH/017kcFm/NrechiizH1wAn6b
6bRZRX9H3xFZkquP70fkH4IzXHxFkTLDT9Zogr6cYx0Hxan79m+cWs99oLWDxOfL
xKZaCtBrXd3g8BuYfL7+T5yDXftzCPEkqfAdpCqTcYBvW+iR2K7OaOYDzGBo0VnE
kyYLQGPZ4/+PJnOYoF30OzapoNnFpxV0WTOQuDqXa0Niu3ym4opN8wweQvptFB7J
mh6DApcLnaUkf7LqWsUdq/RYf7Ny0YWEyJmlnBs9q6TnT/fxpEXYYoEy4pYMPXrg
sdzMg3k1Twt8Y7+uiu8pBQG146ZLmqXLnzNP7yd9IexGzERpe+8qGz+DymaN+Xc=
=dW4E
-----END PGP SIGNATURE-----