On Wed, 8 Mar 2006, Charlie Brady wrote:
> > So here's a proposal. Create a new directory plugins.usr that will be looked
> > in first for plugins. When you want to modify a plugin just copy it to
> > plugins.usr and edit it. When you create a new plugin, put it in
> > plugins.usr/. When you upgrade then you can just copy over everything.
>
> Or use a good revision control system :-)
>
> Couldn't you just as easily use my.foobar rather than foobar in your
> config/plugins? That would keep the core code simpler.
The last time I tried using a plugin name with a '.' period in it,
it did not work.
What I do is copy 'plugin' to 'pluginnew' and have an appropriate
entry in my config/plugins file, but only one gets run at a time. I can
make changes to 'pluginnew', test it by changing which is commented and
which is run, in the config/plugins file, and when it's working properly,
copy it over the original and change the config/plugins file back. Of
course, I also RCS the original before overwriting.
