Tomasz Chmielewski schrieb: > Falko Trojahn wrote: > > (...) > >>> After all, wpkg.xml is really needed just for "execute once" and >>> revisions for upgrades. >> Yes, seems reasonable. > > Umm, wpkg.xml is used for one more thing: package removal instructions. > > There was some patch long time ago by Gordon Klimm which made that WPKG > used removal instructions from the server, but something didn't work > right, and it was removed... > > IMHO using server-side removal instructions is better, as we can easily > correct them. > Doing so on all clients is problematic. Yes, that's problematic - I've stumbled about this problem, too.
If I've tested a package really good before deploying - including removal - all is fine. But if there is a problem, I have to rise the revision number, without really using an upgrade cmd (first run of wpkg.js), then I have the newer package in wpkg.xml with the right remove cmd(s), and can remove the package (second run). Perhaps we should only make sure that - before removal is really done - wpkg checks the revision of this package on the server, and if it is higher, uses this for removal. Don't know if this works in all situations, but could save us from the second run. Best regards Falko -- Falko Trojahn fon +49-341-3581294 Dipl.-Ingenieur Netzwerke/Support fax +49-341-3581295 SMI Softmark Informationstechnologien GmbH www.smi-softmark.de Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ wpkg-users mailing list wpkg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wpkg-users
