[bind10-dev] Why move functionality out of .py.in files

[Evan Hunt]

> 3. Come up with a better way to do the handling of configure-time
> variables. One way would be to put these as class constants in a
> subclass of the specific module/program. These could be per
> module/program or (imho preferably), as one big one for the whole system
> (like config.h). Yes this would still be generated then, but it would
> only contain constants, and only those set by configure. We would also
> not need the sed scripting anymore, since the only time these should
> change would be when configure is rerun anyway.

Or how about, not a subclass of the specific program, but an importable
module?

import isc.local
[...]
SPECFILE_LOCATION="%s/%s/bob.spec" % (isc.local.datarootdir, isc.local.prefix)

-- 
Evan Hunt -- each at isc.org
Internet Systems Consortium, Inc.