Re: Configuration management, revision 3
On reflection I think you're right, it's not clear the inheritance
buys much save extra complexity. It was only a flippant comment.
How does it all work if there's a simple list of sources of data in a
file in /etc/ where that machine looks for config stuff ? A simple URL
probably works well and allows people to distribute config data with
existing servers. I suppose one ought to specify a directory, and the
package specifies a file(s) within that directory. It seems right that
there should be a flexible map between package and area of config
space, but I think this issue was discussed in another thread.
Cheers,
--
Martin Oldfield.
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to:
- References:
- Re: Configuration management, revision 3
- From: Wichert Akkerman <wakkerma@wiggy.ml.org>
- Re: Configuration management, revision 3
- From: Jason Gunthorpe <jgg@gpu.srv.ualberta.ca>
- Re: Configuration management, revision 3
- From: Wichert Akkerman <wakkerma@wiggy.ml.org>
- Re: Configuration management, revision 3
- From: Raul Miller <rdm@test.legislate.com>
- Re: Configuration management, revision 3
- From: Martin Oldfield <m@mail.tc>
- Re: Configuration management, revision 3
- From: Raul Miller <rdm@test.legislate.com>
- Re: Configuration management, revision 3
- From: Martin Oldfield <m@mail.tc>
- Re: Configuration management, revision 3
- From: Raul Miller <rdm@test.legislate.com>
- Re: Configuration management, revision 3
- From: Martin Oldfield <m@mail.tc>
- Re: Configuration management, revision 3
- From: Raul Miller <rdm@test.legislate.com>