Am 17.12.2011 15:03, schrieb Kristopher Johnson: > Rather than using the standard WPKG Client service, I am implementing > another service that provides some user interaction. I want to be able > to determine whether any new or updated packages are available, and if > so, ask the user whether to install them. > > I am implementing my own service and accompanying UI, but I’d like to > avoid making my own fork of wpkg.js. > > I have my service and the accompanying UI mostly implemented, but I’m > not sure how to implement the “determine whether any new or updated > packages are available” functionality. The only way I’ve found to do > it (without modifying wpkg.js) is to execute it with the “/dryrun” > command-line flag and then check whether the text “Could not process” > appears in the output. This seems to work, but seems hacky and > brittle. > > Can anyone suggest a better way to do this? > Use the latest version of WPKG v1.3.0 and the /query switch. To get a list of all modifications for a host use the following: cscript.exe -Nologo wpkg.js /query:m You just need to parse the output for the pending synchronization events. -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? |