On 03/17/2014 05:28 PM, Martin Gregorie wrote:
On Mon, 2014-03-17 at 15:34 +0100, Axb wrote:
On 03/17/2014 03:12 PM, Bowie Bailey wrote:
On 3/17/2014 9:54 AM, Axb wrote:
download source,
unpack
perl Makefile.PL
make && make install && sa-update
The benefit is having all of the packages controlled by yum/rpm. It
makes it easier to determine what is installed and what the dependencies
are. Building from source, I have to manually track dependencies and
make sure they are all installed so it will work properly.
Quite. I wonder - is there a possibility of the SA project itself
releasing Linux packages (RPM for RedHat and derivatives, .deb for
Debian and derivatives plus whatever package types SUSE uses?
Are you volunteering to manage this?
Every distro/OS has a packaging team. It would make more sense for those
interested, to join your distro_du_jour project and work with them. Why
would the SA project want to reinvent the wheel?
Once set up, this should be fairly low maintenance and not add much
effort, since the package building steps can just be added to the
current release process that currently produces tarballs and, uploads to
CPAN. If Apache would support it, SA could even be its own repo server
for the Spamassassin package(s): its trivial to incorporate additional
repo sources into a RedHat yum configuration and I assume the same goes
for Debian apt-get and SUSE. I'm already using additional RPM
repositories for a few Fedora packages that RedHat doesn't provide.
Just a thought...
There are 3rd party repos wich already offer SA 3.4 rpms. You just gotta
find them AND trust them.
