On Wed, Feb 25 2009, Dominique Dumont wrote:
> So I was thinking that this is a typical case where the upgrade could
> be smoothly handled by Config::Model.
> Of course, there's no miracle. For the merge to work automatically and
> the result to be valid, the semantic of the configuration file must be
> known by Config::Model. This is done by describing the structure and
> constraints of the configuration file in a model (hence the
> Config::Model name).
Do we have an idea of how many configuration files can be
described in terms of such a model? (I generally tend to code
configuration files in a scripting language if the code is written in a
scripting language).
While I suspect a large number of our configuration files are
simple, I fear that a significan chunk of them are fairly complex; and
possibly not amenable to being described in terms of a non-trivial
model.
manoj
--
Drop the vase and it will become a Ming of the past. The Adventurer
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
