Re: Looking at WBEM again

I'm sorry you didn't get any response to your earlier questions. I have been
very inconsistent with keeping up with the mailing list. If I have time
later today I'll go back and see if it's something I can respond to.

Concerning the current CFG... I'm definitely not ready to just "scrap" it
in favor of something different. However, it is true that I haven't been
working on it for a while, and I'm personally not sure what I want to do
with it next. One thing Justin and I have discussed is using a different XML
parser so we can lose the Xerces dependency. For instance, libxml2 is an
alternate parser that has a much wider install base. It would make it easier
for people to get started with the project because it would be one less
dependency to satisfy.

Jason


>>> "C. Gatzemeier" <c.gatzemeier-3immqusGtKI@xxxxxxxxxxxxxxxx> 1/8/04 7:36:28 
>>> PM >>>
Am Donnerstag, 8. Januar 2004 19:26 schrieb Jason Long:
> I just wanted to comment on what I've been up to lately...
>
> Currently I'm revisiting the idea of using WBEM, [...] using
> WBEM would require a radically different middle layer and front-end than
> the current Config4GNU project has.

Hmmm, good to know someone is at least thinking of CFG. I aked a few
questions 
trying to contribute some meta config definitions  some time ago and saw
some 
more questions with no response. 

That said, it feels like you want to scrap CFG for version 2 before
becoming a 
little more testable and releasable.


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html