3,217
edits
Changes
m
* add support for 64 bit Windows systems - see http://bugzilla.wpkg.org/show_bug.cgi?id=93
* make WPKG Client window fit on 640x480 screen resolution - see http://bugzilla.wpkg.org/show_bug.cgi?id=90== Important ===
* possibility to enable more debugging:
** how long each part executed (-pre, -post, wpkg.js etc.)
** exit code of each part
** possibility to log into a file
* testing setting: providing "user" for a network path doesn't work; one needs to add DOMAIN\user or WORKGROUP\user. "Test" button will say that the settings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though (probably, because that path is already mapped by Windows? need to check it)
* add /help and /? switches to wpkginst.exe - it's not a CLI app, so probably it would be quite hard - http://bugzilla.wpkg.org/show_bug.cgi?id=101
* These two may have something in common - generally, offline mode sucks:** sometimes offline mode doesn't detect disconnection properly, i.e., when used in VMware (or: it detects disconnection, but logon delay still waits full time)** on some laptops, WPKG stalls on the first "pre" task. These machines disconnect the network card when running on a battery; however, WPKG hangs even if it's not running on a battery - probably the driver puts the network card in a disconnected state on bootup, and enables it later - this confuses WPKG service.=== Useful ===
* make possible to prevent a reboot or shutdown (i.e., we have a package which installs for 1 hour; when user restarts or shutdown, it only logs him out, installation continues, description/progress window is shown, and machine only shutdowns/reboots when everything is done)
* upgrading WPKG Client from WPKG Client is not that easy (file in use, can't upgrade myself!)
→WPKG Client
== WPKG Client ==
* restarting These two may have something in common - generally, offline mode sucks:** sometimes offline mode doesn't detect disconnection properly, i.e., when used in VMware (or: it detects disconnection, but logon delay still waits full time)** on some laptops, WPKG stalls on the service locally from within first "pre" task. These machines disconnect the wpkginstnetwork card when running on a battery; however, WPKG hangs even if it's not running on a battery - probably the driver puts the network card in a disconnected state on bootup, and enables it later - this confuses WPKG service.exe
* restarting some laptops have only wireless connections which is enabled much later. Wait until a network connection is available - what to do with the service on remote machines logon delay then? * upgrading WPKG Client from within the wpkginst.exeWPKG Client is not that easy (file in use, can't upgrade myself!)
* some more integration with wpkg.js: wpkg.js should be able to pass information to WPKG Client:
** start selected installers with GUI (some installers break if not started with a GUI) - seems to be very complicated, and wpkg.js was already started in the background - not sure if anyone needs it- probably we don't need this one at all
** parse output of wpkg.js (STDOUT) and display programs which are being installed
* some laptops have only wireless connections which is enabled much later. Wait until testing setting: providing "user" for a network connection is available - what path doesn't work; one needs to do with add DOMAIN\user or WORKGROUP\user. "Test" button will say that the logon delay thensettings are correct even when we don't specify DOMAIN\ or WORKGROUP\ though (probably, because that path is already mapped by Windows?need to check it) * make possible to prevent a reboot or shutdown (i.e., we have a package which installs for 1 hour; when user restarts or shutdown, it only logs him out, installation continues, description/progress window is shown, and machine only shutdowns/reboots when everything is done)
* make possible to execute everything on machine shutdown - with the same description/progress window as with logon delay
=== Boring / easy, but useful === * command line tool add support for creating a crypted password (both 64 bit Windows and UNIX version) systems - see http://listsbugzilla.wpkg.org/pipermail/wpkgshow_bug.cgi?id=93 * make WPKG Client window fit on 640x480 screen resolution -userssee http:/2008-April/003213bugzilla.html for example codewpkg.org/show_bug.cgi?id=90
* F1 launches "help file not found", should open help website
=== Do we need this? ===
* restarting the service locally from within the wpkginst.exe
* restarting the service on remote machines from within the wpkginst.exe
* possibility to enable more debugging:
** how long each part executed (-pre, -post, wpkg.js etc.)
** exit code of each part
** possibility to log into a file
* add /help and /? switches to wpkginst.exe - it's not a CLI app, so probably it would be quite hard - http://bugzilla.wpkg.org/show_bug.cgi?id=101 - display a help window would be the easiest
=== Already done ===
* command line tool for creating a crypted password (both Windows and UNIX version) - see http://lists.wpkg.org/pipermail/wpkg-users/2008-April/003213.html for example code
== WPKG web interface ==
[http://wpkg.linuxkidd.com WPKG web interface] currently needs a maintainer. If you're interested, please let us know both on wpkg-users@ and wpkg_web_users@ [[Support|mailing lists]].