On 03/17/2014 03:12 PM, Bowie Bailey wrote:
On 3/17/2014 9:54 AM, Axb wrote:
On 03/17/2014 02:28 PM, Bowie Bailey wrote:
On 3/17/2014 2:27 AM, Amir Caspi wrote:
On Mar 17, 2014, at 12:12 AM, Thomas Harold <thomas-li...@nybeta.com>
wrote:
Well, for simplicity, RPMForge is probably the easiest, even if it
doesn't have the latest versions. Latest CentOS6 x64 version is
3.3.1.
rpmforge-extras has v3.3.2. Atomic also has it. Nobody has 3.4 yet.
3.4 was released over a month ago at this point and should not be a
difficult package to build. Maybe I'm just expecting too much. What is
the general lag time for an updated package to make it into the repo?
Guys,
What's the benefit from installing from RPM?
Is waiting for a distro's release better than:
download source,
unpack
perl Makefile.PL
make && make install && sa-update
IMPORTANT: if you do this and are running a rpm install, make sure to
remove it before installing from source or you'll have a bunch of
orphans....
If you want to install in non standard paths, there's command line
switches.
Installing from source also allows you to do a quick upgrade from trunk
if you decide you need a that special bug fix which hasn't been released
by the distro..
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.
If I use packages from a repo, all I have to do is "yum install
spamassassin" or "yum update spamassassin" and any dependencies are
automatically taken care of for me. I can also issue a simple "yum
update" and update everything on the system without having to remember
to go back and grab the SA update separately.
If I build the rpm package myself, I lose some of the convenience of the
upgrade, but I can still take advantage of the package management and
dependency tracking features.
It just makes management much simpler.
simpler maybe, but leaves you at the mercy of other ppl's schedule.
In the cases of SA & ClamAV I prefer control over simple.
I may build from source anyway just so I can keep it current. I can
deal with a bit of a lag with SA, but I'd prefer to update it within a
month or so. I'm already installing ClamAV from source so I can make
sure to keep it current (don't want any lag at all on that one).
Just remember to do the yum remove before installing from source, unless
you take time to set all paths as RHEL does.
If you run spamd, you may want to save your init script & options/paths.
make install won't install one for you.
