On Wed, 2 Nov 2005, John Peacock wrote:

> > When should we expect the new version?
>
> When it's done?  <duck>

        "Quack!" ;-)

        Just trying to get an idea of what's going on and what, if
anything, is being waited for. Explanation appreciated.

> >     I have almost 20 plugins that are nearly all very customized for
> > special purposes. I may have one or two that are still running stock
> > from the distribution. I'll likely have to rewrite all of them for the
> > new version (or even just the latest version). Is there a concise and
> > readable discription of these plugin format changes and possibly a
> > simple method of changing them?
>
> The older plugins should work just fine with little or no modification.
> The changes Matt was referring to were just a way to make it easier to
> write plugins.  You no longer have to use register() if you name your
> action subs hook_* (so hook_rcpt will fire in the rcpt hook).

        That's very helpful. Should simplify things until I can budget
some time to revamp the old plugins.

> I'd recommend you do what I do (these are all untested commandlines but
> probably pretty close to what would work):

> 8) Remember to sync your mirror once in the while to get the new shiny
> things I have added...

        Actually, this is mostly why I want to stick with a stable release
- I don't know how all these shiny things may affect, or be affected by,
the customized code I have. But I'll think about it. Thanks.

        Well, I still need to get a few things working on the new server,
so I can wait a bit longer. If it gets to be too long, I'll probably just
use the latest stable and be done with it (until next time I build a new
server - I'm expecting/hoping that core products/apps will stand on their
own until the powers that be decide to upgrade to a new system, so I don't
have to keep upgrading (I'm not talking fixes here, of course)  when I
could be working on more important stuff).

        Back to lurking. Thanks :-)

-- 
Roger Walker
"HIS Pain - OUR Gain"

Reply via email to