----- Message from Amir Caspi <[email protected]> ---------
Date: Sat, 3 Apr 2021 22:06:03 -0600
From: Amir Caspi <[email protected]>
Subject: Re: Update SA on CentOS
To: [email protected]
Cc: [email protected]
On Apr 3, 2021, at 9:15 PM, Simon Wilson <[email protected]> wrote:
And then you are not stepping away from one of CentOS's main
advantages - stable packages not built outside of RPM.
For what it's worth, using the Fedora package has been exceedingly
stable on my CentOS 7 system. SA is extensively tested by the dev
team before release, and there is very little that is
system-specific so building from the SRPM is easy and
straightforward. Installing really is as simple as the four steps I
included in the prior email, and I've been running SA that way on
CentOS systems for years (from CentOS 5 onwards).
Granted, I am just one person and my setup is unique to me, so my
experience may not translate to others. But I've found the SA
package to be completely stable. (Note that it's still built
"inside" the RPM, because it's built from the SRPM used for Fedora.)
Cheers.
--- Amir
Sure - completely get that.
My point is installing the latest version of SA *on its own* without
understanding what is causing the increased spam volume is unlikely to
just fix anything...
Identify what is causing the increased spam, then assess whether there
is anything in SA 3.4.x which is designed to address that. If the
answer is yes a newer version will address it - then by all means
proceed down the path of packaging it if prepared to do so.
The first step (on CentOS at least) should not be to package up
non-CentOS releases - if that *is* your first step then CentOS is not
the distro you should be using...
CentOS / RHEL backport critical security fixes into the stock
versions... you lose that as soon as you go 'roll-your-own'. Not
insurmountable I know - but you need to have a far more rigorous
process for keeping aware and following through / re-packaging.
In other words - my comment to the original poster here is work out
what the problem is before assuming that a new version will fix it.
Simon.
--
Simon Wilson
M: 0400 12 11 16
