This is sort of on topic for users, but I'm more than happy to move it
to 'dev' if appropriate.

What I'm trying to do is to create a basic GUI that allows me to detect:

1) What modules are installed on the system
2) What classes are in the modules
3) What defines are in the classes
4) What defaults/requires are in place in the defines
5) Anything in a general manifest that is outside of a module (secondary)

I started down a path of trying to detect all of this myself and then
realized that I'm being a bit stupid since that entire logic structure
is present in the Puppet compiler.

Unfortunately, I've been wading through the code with very little luck
at figuring out how to hook/call/override (whatever) this logical
segment of the Puppet code.

Am I going down the right track and, if so, how would I tap into the
Puppet compiler in this way?

Alternatively, would it just be easier to collapse the modules/manifests
and parse them from there?

Thanks for the indulgence, I intend to release this thing if I ever get
it to a state that is actually useful.

I'm writing it in using a GTK+/Ruby combo since QT makes my hair stand
on end.  I'm also writing it in my spare time, so who knows how long it
will take.

Thanks for any help that is offered.

Trevor

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to