pseudo-install has been modified in a way so it updates
LocalSite.cfg activating the plugins that were pseudo-installed.
That is a very unwanted feature.
It is common to pseudo-install more plugins than you activate via configure.
I need that for testing plugins. I cannot spend time running pseudo-install each time I need to disable a plugin.
On test servers the pseudo-install runs regularly via cron and it should NEVER EVER do anything that changes the server configuration.
Please revert this feature ASAP
--
TWiki:Main/KennethLavrsen - 04 Nov 2007
If it was an unwanted feature, i wouldn't have added it. When you are developing/testing plugins, the ability to quickly and cleanly install and uninstall is very important. pseudo-install respects an existing enabled setting in
LocalSite.cfg and will not activate a plugin that was previously explicitly deactivated.
To the best of my knowledge, and certainly in my experience, it is
not common to pseudo-install more plugins than you activate (or explicitly deactivate). If a plugin is not enabed
it is not complied, so by installing all plugins the only thing you are testing is that none of the plugins overwrites core files - and if you install -force, you don't even know that, until it crashes mysteriously.
However I just don't have the energy to argue about this, so I reverted the default behaviour.
CC
I guess it was the presence of the pseudo-install
all that created the problem. Combined with the activation of the plugins it became a horror. If you pseudo-install with a small list of plugins the problem was not so severe because you had cleverly made it not activate a plugin if the setting was already there and =0
--
TWiki:Main.KennethLavrsen - 05 Nov 2007