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

[simplesi]

Rainer Meier wrote:
> 
> 
> Could you explain this "certain circumstances" in a bit more detail
> because it
> might be a bug. I've checked the code and wpkg.xml entries are only
> removed in
> the removePackage function. And all of them are completely skipped if the
> /noremove flag (or noremove config) is set. In this case no remove
> commands are
> executed at all and wpkg.xml is not touched at all.
> 
Are you saying the documentation is wrong and that /noremove will not remove
packages under any circumstances?
from wpkg.js 1.1.2


> 
> /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


> "	Note that each package which is requested to be removed (manually or by
> \n" + 
> "	a synchronization request) will be checked for its state by executing
> its \n" + 
> "	included package checks. If the package has been removed manually it
> will \n" + 
> "	also be removed from the settings database. Due to the fact that
> packages \n" + 
> "	whithout checks always return 'false' for during the install-status
> check \n" + 
> "	these packages will disappear from the local wpkg.xml. \n" + 
> "\n" 
> 

regards

Simon
 
-- 
View this message in context: http://www.nabble.com/-Bug-175--New%3A-Test-return-value-of-removeSettingsNode-function-tp25737803p25742689.html
Sent from the WPKG - Users mailing list archive at Nabble.com.