Falko Trojahn wrote: (...)
>> If I saw WPKG for the first time, I'd ask why is it necessary - why the >> packager doesn't know what packages are installed? >> We know the answer, but from the "average Joe" perspective, it might be >> a bit unclear. And average Joe might be right - Office is in Software >> Add/Remove, right? >> >> As the tests are rather inexpensive, both in terms of system load and >> time, perhaps it would be a good idea to make checks for *all* available >> packages each time WPKG is started (unless overridden with something >> like /nochecks)? > Yes, I thought about that, too. But what would "average Joe" think about > this switch - "what's that for"? Perhaps the check should be done every > time, anyways. It would be described in /help (and on the website). Perhaps, we could distinguish between normal and "advanced" options. Advanced options IMO are at least: /rebootcmd:<option>, /forceinstall, /norunningstate. > Pro: check every time is perhaps better than not to check, since the > problem often can be between keyboard and chair ... ;-) > Contra: another command line option ... > >> After all, wpkg.xml is really needed just for "execute once" and >> revisions for upgrades. > Yes, seems reasonable. Good that we agreed in a democratic way after a long discussion with many participants :) -- Tomasz Chmielewski http://wpkg.org 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
