[wpkg-users] [Bug 114] new parameter /force2 ?

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=114





--- Comment #3 from Jens Geile <jens.geile at mzbs.de>  2008-05-08 12:58:27 ---
I'm mainly using /force to make sure noone installs any software that is WPKG's
package database manually.
All on a machine installed software that can be maintained with WPKG should be
maintained with WPKG.

Example:
One profile doesn't contain "Firefox" for one or another reason. Some local
administrator who doesn't know about those reasons decides that he wants to
browse with Firefox on one of the machines from that profile so he installs
Firefox manually. Without using the /force parameter WPKG will never get to
know about Firefox being installed on that machine and thus won't remove it
from that machine again.

Using /force helps me to always have the machines in a state conform with the
profile for that machine (at least for the software in the package database).
It also doesn't always execute the <install...> command on each run if it
detects that the software in question is already installed in the current
revision.

What I want/need is a second /force command that basically does the same as the
current /force but uses the local wpkg.xml first to detect whether a previous
version of the software is already installed and then issues the <upgrade..>
command instead of the <install..> command.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.