Yum/RPM install

[Peter Nitschke]

Julian, I wasn't thinking of you changing what already works, I was just
wanting to clarify whether I would be heading for any problems if I do it
myself with RPM's.

For me, it's a comfort level thing.  I am comfortable with RPM's as I know
how to install/upgrade/remove them, see what's there and what version, and
it's easy.  I can also make my own repo for the servers I manage and
upgrade them all faster by adding eg a new MailScanner RPM to my local
repo.  I will still need to log into the servers to make any conf changes
(though that could probably also be scripted), but I won't have to log in,
manually download the latest package, untar it, run install.sh and then
wait while it re-compiles everything even when some or most of the required
modules exist, and then check the conf files.

I know this is only workable for me once I have moved all the servers to
the same OS, but I am trying to get some of my life back.  :)

The only thing that would make it easier, would be comments in the
changelog about anything outside of the RPM that I need to pay attention
to, eg settings that get added to other files such as v320.pre etc.

Cheers,

Peter




*********** REPLY SEPARATOR  ***********

On 13/08/2007 at 6:17 PM Julian Field wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>How about this?
>
>Would you like me to create another ClamAV+SA distribution that used 
>SRPMs in the same way my MailScanner install script does?
>
>It will take a bit of work on my part to build all the RPMs, but easy 
>enough to maintain once I've got it there.
>
>Does that help you, or not? I'm not going to waste the effort, it's a 
>significant amount of time.
>
>Peter Nitschke wrote:
>> Which is why I like the concept of doing it all with RPMs.
>>
>> Most are available on the major repo sites, the handful that aren't I
>have
>> let Julian's script create, then made a local repo for them so I can do
>> repeat installs simply and quickly to other PC's.
>>
>> I realise this is OS specific, but most of us with multiple servers to
>> manage have probably standardised on a particular OS, in my case Centos
>5.
>>
>> The MS install script pretty much creates then installs everything as
>> RPM's, and the recent SA/Clam install script recommends using clam
RPM's,
>> so I figure that going the last step to all RPM's makes good sense.
>>
>> Julians scripts do a few tweak, eg to SA v3xx.pre files which is easy
>> enough to duplicate, but would I be missing anything else?
>>
>> My thoughts are towards lower manual maintenance by being able to do
>future
>> upgrades all by RPM, and by being able to create servers with a known
>> predictable setup which doesn't tend to happen if you configure them all
>> individually.
>>
>> Peter
>>
>>
>> *********** REPLY SEPARATOR  ***********
>>
>> On 13/08/2007 at 5:33 PM Gareth wrote:
>>
>>   
>>> Managing perl modules would be a real pain as you would practically
have
>>> to
>>> install them as separate RPM's aswell. RPM has its own versioning and
>>> upgrade system which perl also has. Trying to mix them both at the same
>>> time
>>> can cause lots of issues.
>>>
>>>     
>>>> -----Original Message-----
>>>> From: mailscanner-bounces at lists.mailscanner.info
>>>> [mailto:mailscanner-bounces at lists.mailscanner.info]On Behalf Of Peter
>>>> Nitschke
>>>> Sent: 13 August 2007 17:22
>>>> To: mailscanner at lists.mailscanner.info
>>>> Subject: Yum/RPM install
>>>>
>>>>
>>>> There have been a few threads on the issue of making more use of
>>>> yum and or
>>>> RPM's to install MailScanner and SA/Clam-av, but none of them seem to
>>>>       
>>> have
>>>     
>>>> come to any real conclusion.
>>>>
>>>> Is there any real disadvantage to doing it all with RPM's rather than
>>>> having all the modules compiled with each install or upgrade?
>>>>
>>>> Peter
>>>>
>>>>
>>>> --
>>>> MailScanner mailing list
>>>> mailscanner at lists.mailscanner.info
>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>
>>>> Before posting, read http://wiki.mailscanner.info/posting
>>>>
>>>> Support MailScanner development - buy the book off the website!
>>>>
>>>>
>>>>
>>>>       
>>> -- 
>>> MailScanner mailing list
>>> mailscanner at lists.mailscanner.info
>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>
>>> Before posting, read http://wiki.mailscanner.info/posting
>>>
>>> Support MailScanner development - buy the book off the website!
>>>     
>>
>>
>>
>>   
>
>Jules
>
>- -- 
>Julian Field MEng CITP
>www.MailScanner.info
>Buy the MailScanner book at www.MailScanner.info/store
>
>MailScanner customisation, or any advanced system administration help?
>Contact me at Jules at Jules.FM
>
>PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>For all your IT requirements visit www.transtec.co.uk
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP Desktop 9.6.2 (Build 2014)
>Charset: ISO-8859-1
>
>wj8DBQFGwJIaEfZZRxQVtlQRAlPCAKDqmUB748A5UHmQ+UAiVGI5NBa9zwCfYcLd
>2j+Gr0bpvn2D+Ao1Thhc+9s=
>=Vh2+
>-----END PGP SIGNATURE-----
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>For all your IT requirements visit www.transtec.co.uk
>
>-- 
>MailScanner mailing list
>mailscanner at lists.mailscanner.info
>http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>Before posting, read http://wiki.mailscanner.info/posting
>
>Support MailScanner development - buy the book off the website!