[bind10-dev] location of specfiles in source tree

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

I just got handed an old ticket (http://bind10.isc.org/ticket/243), in
which I suggested to group all .spec files in the source tree.

I think this has so far been just an idea of mine, and not discussed
yet, so let's do that now :)

The problem is this; if we ever want to do offline configuration
(offline here meaning both non-running modules and configuration
through bindctl if bind10 is not running at all), we'll need to be
able to know what modules exist and what configuration they (can)
have. So an obvious way to do that would be to read all known
specification files.

In the installed directory; this would be easy, they are placed
together in one directory. In the source tree, however, this would not
(since they are all, quite logically, placed with their module).

So as a very first step towards this functionality, I suggested to
make something like a src/specs/ dir and put them all there.

Now of course it isn't strictly necessary; we can make some smart
search for .spec's (but, well, ew.), or perhaps we don't even think
we'll need this when running from source (as soon as you enable a
module, it's configuration will become known anyway, which is
behaviour i want to keep anyway). A run-time command or config option
(or both) to add to a 'module_spec' path would also be a valid option
IMO (though there is a bit of trickiness there). There are more
approaches btw.

Now there is also the question; what about out-of-tree modules?
Depending on the approach chosen, this may or may not be a problem;
should one want to add a new module to the system, it will have to
make the system know about it in one way or another anyway; either by
running it or by informing the configmanager of the location of its spec.

Any thoughts?

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk89KhIACgkQ4nZCKsdOncXneACfQd6cpqmm29s+90m6TWDYrZJa
XPsAn1R8I9AWP6kxdWIzZRAp/tEYNjDG
=x6C3
-----END PGP SIGNATURE-----