http://bugzilla.wpkg.org/show_bug.cgi?id=114 --- Comment #5 from Jens Geile <jens.geile at mzbs.de> 2008-05-08 14:56:55 --- > > I'm mainly using /force to make sure noone installs any software that is > > WPKG's package database manually. > I think you mean you want to assure that nobody installs software which is NOT > assigned to a host. Why not simply removing the permissions from the user > account to install software? I cannot just remove the permision to install software from the local administrator or the domain administrator accounts... > > All on a machine installed software that can be maintained with WPKG > > should be maintained with WPKG. > This you can only assure if nobody has the rights to install software locally. Normal users cannot install software, but local/domain administrators can and should be able to do so at any time (except for software that can be installed with WPKG). > Now I am slightly confused. Of course WPKG does not know about every package > which will be installed manually. But /force does not change this behavior at > all. /force will just make WPKG to disregard the local wpkg.xml and start over > to install all assigned software packages. Depending on defined checks it > might detect that a sofware is already installed and it will not re-install > it. Never ever WPKG is going to remove software on the system which is not > assigned to the host but installed unless WPKG knows that it has been > installed by WPKG before (by looking at wpkg.xml). If you use /force then > exactly wpkg.xml is disregarded, so WPKG will never ever uninstall any > software when /force is used. Ok, let me show you what WPKG is actually doing: Since the log files are so long I've posted them here: http://pastebin.org/34676 (If I missed an important case just tell me what you want me to test and I''l provide the log) See the 6th and 7th case where Firefox is not in the profile but installed on the machine and WPKG removes it when the /force parameter _IS_ used but not when /force _IS NOT_ used > You want to have a way where WPKG removes any installed software which is not > in the distribution list. This is not possible at the moment. I want to have a way where WPKG removes any installed software which is in packages.xml but not in the local wpkg.xml. > Unless Firefox would be installed using WPKG as well - but I understood your > comment that the local user is installing Firefox manually (by packages > downloaded from the web page). Yes. > /force just makes WPKG to re-evaluate the state of each package and install > packages missing from the system. In /force mode WPKG will neither remove any > package (since it does not know about the previous state) nor will it execute > any upgrade (due to the same reason). Well, obviously (7th case) WPKG does remove packages from the system when using /force. > But remember - there is still no way to detect a manually installed Firefox on > the system and to remove it by WPKG. WPKG can only uninstall packages which > are installed by WPKG. The reason is simple - WPKG cannot know how to > uninstall any software on this planet as every software uses different > installers... So there is no way to get rid of such a manually installed > Firefox in an automatic way. This is where you are wrong. I'm not talking about "any software on this planet" but about "software specified in packages.xml" here! Firefox _IS_ in packages.xmlm WPKG _DOES_ know how to uninstall it and /force does exactly that. > Even your request does not change this fact. Maybe I didn't manage to explain well enough what I want. I want a mode that re-evaluates every package's state on the machine. A mode that does exactly the same as /force at the beginning but that does not execute the <install...> command but the command appropriate for the current state of the package: - If the package is not installed on the machine and not in the profile --> Do nothing - If the package is not installed on the machine but in the profile --> Install it - If the package is installed on the machine but not in the profile --> Remove it - If the package is installed on the machine, in the profile and in the local wpkg.xml --> Compare version and either update or leave it as it is - If the package is installed on the machine, in the profile but not in the local wpkg.xml --> Compare version of installed package and either update or leave it as it is I hope I managed to make it a little clearer as to what i want. ;) -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |