Nicholas Young schrieb:
In an attempt to write up some scripts to allow simple management of the various XML files, I think the easiest way, for me, is to use perl.At the moment the vague plan is WPKG.pm -> WPKG::Hosts.pm -> WPKG::Packages.pm -> WPKG::Profiles.pm The client management code, ie cgi page will call WPKG.pm which will open the xml files using the other three modules. A skeleton of WPKG::Profiles is included below for a brief idea of what I am thinking. The client code will essentially run $wpkg = new WPKG("Directory"); $wpkg->add_host("foobar", "custom"); $wpkg->add_profile_package("custom", "msoffice"); The modules then will do all the magic in ensuring that "msoffice" exists and that "custom" is a valid profile-id. Or direct addressing if required in: $wpkg->{packages}->{wpkg1}->{name} = "Windows Packager sample 1"; The main aim is to make writing a web interface "easy" as it is all calls against perl modules which should strip requirements for worrying about concistency/XML formatting/... Any problems, suggestions before I go further with writing this?
there will be problems for sure when you first release it :)) but go ahead, I can certainly help at least in testing. -- Tomek http://wpkg.org ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ wpkg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wpkg-users
