amavis stable release 2.14.0

[Noel Butler]

On 12/07/2025 23:17, Michael Orlitzky wrote:

> On 2025-07-12 16:03:45, Nick Edwards wrote:
> 
>> You have nuked the simple plain install file, there is no instructions 
>>  on
>> how to install it, oh theres some crud that looks like it was written 
>> by a
> 
> dzil is the front-end for DistZilla. As the very first page of its
> documentation says, dist.ini tells it what to do, and the reason it's
> recommended is because it knows where to put all of those perl lib
> files that you are complaining about not knowing where to put.
> 
> If you really want to install amavis by hand, the old installation
> instructions have not changed much. The only new step is that you have
> to install the perl libs Amavis.pm, Mail/*.pm, and Amavis/*.pm to
> wherever on your system such things go.

I've not upgraded since 2.11, meh, it works fine, and with over a dozen 
mx-in's and half as many smtp-outs's, I'm not keen on us updating 
anything that's not got a critical bug anyway, that said, I've a couple 
of points after reading OP's comments.

distzilla as far as I knew was more for those packaging cpan modules, 
not for installing stuff like this, but I've never given it anything 
more than cursory look a few years back during lockdowns for 
the-thing-we-dont-discuss to pass time.

Secondly, it concerns me too there is no documentation on this change in 
any news or release file, Mark's site certainly says nothing about it, 
but that's no longer updated anyway since he has stepped away.

Since many of us install manually (don't be fooled into thinking 
everyone uses redhat and debian) the old installation instructions 
actually said where things should go, like /u/l/sbin, it's feasible to 
want to know if that's where it still puts the scripts in the event one 
needs to upgrade some day, looking at 2.14 dist.ini, it says nothing at 
all about where the executable scripts go, so IMHO, that's a genuine 
question.

I can understand others concerns, so I'd ask the question how does it 
know where to place them?  Will it use /u/l/sbin, /u/l/bin, /u/bin, 
u/sbin, the ini file certainly doesn't tell you, perhaps the OP might 
have been trying to ask this to avoid conflicts, but asked with way too 
much emotion so didn't get his point across.

My suggestion is the project create a new install file explaining all 
this, and add it to the release notes, since this is usually the first 
look for admins to ensure they avoid breakage when updating, and if it 
makes point about such changes, one then tends to go looking for 
UPDATE/UPGRADE section in INSTALL, or NEWS files.

-- 
Regards,
Noel Butler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.amavis.org/pipermail/amavis-users/attachments/20250713/b825320a/attachment.htm>