MailWatch and CustomConfig.pm

[Julian Field]

At 07:55 23/03/2004, you wrote:
>On Monday, March 22, 2004 3:19 PM Julian Field
><mailto:mailscanner at ECS.SOTON.AC.UK> wrote:
>
> > When you install the RPM of MailScanner, it shouldn't
> > over-write CustomConfig.pm if you have changed it anyway. Are
> > you saying that it always gets over-written even when you have
> > changed it?
>
>My port does. The only things I do not overwrite automatically are
>config-files, reports, wrappers and autoupdate-script. Libs etc. are
>always brought uptodate. If I do not do this and you decide to change
>CustomConfig.pm the user will then have to adjust the system.
>
>I just saw you are going to implement this. Thanks!

There is now a /usr/lib/MailScanner/MailScanner/CustomFunctions directory.
Any files placed in there (whose names don't start with a "." and don't end
with a ".rpmnew") will be used as files full of CustomFunctions code.

So you can have 1 file per Custom Function if you like. Steve might want to
use this directory in his MailWatch installer, for example.

The only file put in there to start with is "MyExample.pm" which is the
commented-out example from CustomConfig.pm. CustomConfig.pm is still there
and is still used, so no-one's setup will break. But you are encouraged to
use the "CustomFunctions" directory in future.

This will be in the next beta, which you can expect shortly...
--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654