[wpkg-users] Will WPKG uninstall software it did not install?

Peter Gough pmgough at gmail.com
Sat Feb 27 01:40:06 CET 2010

Agreed but this isn't the scenario I was describing.

Simply put if for some reason I decide to rollout Firefox v3.5 to all of my
clients but some of my users have already installed v3.6 then wpkg may
install the older version over the top of the newer version assuming I use a
check condition that specifies the file version as v3.5..

In this scenario wpkg.js would check for the v3.5 file and when it doesn't
find it then it would attempt to install v3.5 using the install commands in
the package definition file, regardless of whether v3.6 is installed or not.

That's why I was recommending being very careful when writing check
conditions and running a full test and a small pilot group first before
implementing wpkg.

On 27 February 2010 09:22, Rainer Meier <r.meier at wpkg.org> wrote:

> Hi Kevin,
> On 26.02.2010 23:19, Kevin Keane wrote:
> >> WPKG does __not__ scan the installed software and remove anything,
> >> which does not match the profile of the computer.
> >
> > To be honest, I don't completely trust WPKG in this respect. I have never
> been able to conclusively determine any scenario, but I could have sworn I
> had seen WPKG remove software that had never been part of the profile (even
> after we discussed it on this list a couple months ago).
> This would be quite magic since there is no code in wpkg.js to scan for
> software
> which is not within the profile assigned to the host and which was never
> part of
> the profile.
> So WPKG does never touch any part of the system which is not under its
> control
> (means not within the profile at any time). WPKG also never executes
> commands
> you didn not specify within the package definition. So if you do not have
> any
> commands which could make WPKG to remove Firefox it will never be able to
> remove
> it. Even if you have a Firefox package in your packages.xml which is NOT
> assigned to the host WPKG will never ever run any of these commands unless
> you
> assign that package to the host at least once.
> If you find a reproducible case where WPKG would "invent" some
> code/commands
> please let me know, I would be very interested to analyze it.
> br,
> Rainer
> -------------------------------------------------------------------------
> wpkg-users mailing list archives >>
> http://lists.wpkg.org/pipermail/wpkg-users/
> _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/wpkg-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20100227/8baa32a5/attachment-0002.html>

More information about the wpkg-users mailing list