[wpkg-users] [Bug 175] Test return value of removeSettingsNode function

Rainer Meier r.meier at wpkg.org
Mon Oct 5 00:07:11 CEST 2009


Hi Simon,

simplesi wrote:
> Are you saying the documentation is wrong and that /noremove will not remove
> packages under any circumstances?
> from wpkg.js 1.1.2

Which part of the documentation is wrong? The one you quote below...


>> /noremove \n" + 
>> "	Disable the removal of all packages. If used in conjunction with the \n"
>> + 
>> "	/synchronize parameter it will just add packages but never remove them.
>> \n" + 
>> "	Instead of removing a list of packages which would have been removed \n"
>> + 
>> "	during that session is printed on exit. Packages are not removed from
>> \n" + 
>> "	the local settings database (wpkg.xml). Therefore it will contain a list
>> \n" + 
>> "	of all packages ever installed. \n" + 
>>
> and this is the bit that causes me problems

I don't think this causes any problem - this is just the printout of the usage
screen ;-)
Well I think you want to point out something within the text. Which parts do you
think are wrong?
I was under the impression that you would like WPKG not to remove any package at
any point in time. This is what the /noremove flag is supposed to do I think
(unless there is some other misunderstanding).
Especially it reads "Packages are not removed from the local settings database
(wpkg.xml). Therefore it will contain a list of all packages ever installed."
Which seems to be what you like to achieve, isn't it?


br,
Rainer



More information about the wpkg-users mailing list