To now make this relevant to cfengine :), imagine if we had a (first-level) package API that had commands named after the basic operations, ie. PackageInstall, PackageRemove, PackageUpgrade, PackageVersionCompare, and the like, and they had a configuration
file which defined a command to run for each of them, and possibly
some control over getting information from them afterwards. If we
had a library like that, we could just add things to the config file,
and they would work.
This is more or less what I had in mind, without the idea of a cross-platform library. Just have a cfengine configuration environment that defines the various operations, and allow it to be defined on the fly during a cfengine run.
-- David Douthitt UNIX System Administrator Linux+, LPIC-1, RHCE HP-UX, Unixware, Linux, FreeBSD, OpenBSD Member: ACM, USENIX/SAGE
_______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
