When you work on a patch release like from Release branch we only have the default plugins.

When you want to test your non-default plugins you need to install them from trunk.

I would like to be able to do this using pseudo-install.pl in the Release branch but with a --extension-path=/path/to/trunk-svn-checkout or similar.

My idea is that you first run a normal pseudo-install, and then new runs installing the additional plugins from trunk.

If I do a checkout of something from trunk inside twikiplugins it becomes a mess. I prefer that my co tree is clean so I can svn commit from the svn root.

I currently run with a hacked version of pseudo-install with hardcoded path so I am not in a panic. But I cannot be the only one with this need.

-- KennethLavrsen - 06 Nov 2008 - 00:00

There is an (undocumented?) feature of pseudo-install.pl: It adds the path of the environment variable TWIKI_EXTENSIONS to the beginning of path used to install the plugins. So, if you want to test plugins from trunk, just set that variable to the appropiate value. If you're using an standard svn co layout in /home/foswiki, I suggest you to use the following:

export TWIKI_EXTENSIONS=/home/foswiki/branch/Release/twikiplugins:/home/foswiki/trunk

This will make pseudo-install.pl to look first in the release plugins and then in the trunk plugins.

-- RafaelAlvarez - 06 Nov 2008 - 01:32

I don't trust ENV vars (personal choice) so would like pseudo-install in a release branch look to see if ../branches and thus ../trunk exist (ie to test if its a full checkout of svn) and if so 'just dwim', with suitable warning of course. -- SvenDowideit - 06 Nov 2008 - 04:40

Setting this to No Action.

• We are converting to git.
• pseudo-install will automatically fetch missing extensions from github.

-- GeorgeClark - 30 May 2014