[PATCH] 4.0: New build system doesn't allow custom config file locations

[David W. Hankins]

On Tue, Sep 02, 2008 at 03:32:11PM +0100, Tony Vroon wrote:
> On Mon, 2008-09-01 at 16:45 +0100, Tony Vroon wrote:
> > The old build system allowed to customise the location of several key
> > configuration files through modifying variables such as _PATH_DHCPD_CONF
> > and _PATH_DHCLIENT_CONF.
> 
> Withdrawn. It is ignored at the installation stage.

The configs are examples only and shouldn't be installed (they are not
"default configs")...do you mean the paths are built in to the
binaries that are installed?

> I have a stack of about 7 patches here, of which perhaps 3 or 4 would be
> upstream-worthy. Does anyone read this list?

dhcp-hackers is intended more for generic "IETF DHCP" related
development.

If you want to discuss ISC DHCP development specifics, the list you
want is dhcp-workers at isc.org.

If you just want to submit patches our ticketing systems are better,
dhcp-suggest at isc.org is for feature enhancements, dhcp-bugs at isc.org
for bug reports.


In the new autoconf system, we permit the leases and pid files to be
over-ridden.  It seems like an oversight that the config files aren't
included in that.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
-- 
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins