5 messages in net.sourceforge.lists.courier-imapRe: [Courier-imap] Updating/Refreshin...| From | Sent On | Attachments |
|---|---|---|
| Jason Williams | Dec 16, 2003 9:36 am | |
| Tony Earnshaw | Dec 16, 2003 10:44 am | |
| Jason Williams | Dec 16, 2003 11:56 am | |
| Sam Varshavchik | Dec 16, 2003 5:07 pm | |
| Sam Varshavchik | Dec 16, 2003 5:08 pm |
| Subject: | Re: [Courier-imap] Updating/Refreshing Courier-IMAP packages | |
|---|---|---|
| From: | Jason Williams (jwil...@courtesymortgage.com) | |
| Date: | Dec 16, 2003 11:56:30 am | |
| List: | net.sourceforge.lists.courier-imap | |
Hello and thanks for the reply.
Sam (he's off to Denmark?) would say "don't compile your own on RedHat" and in fact that's what the source compile "configure" will tell you, in no uncertain terms, unless you tell it to shut up - like I do.
I do recall reading the docs and it suggesting that if you do run Red Hat, the best option is to build the rpms. (Which is what I originally did. :) )
There are those who can configure and compile their own stuff and have confidence in doing so - I'm one of those. Then there are those who swear by up2date and such things - that will break your own source or rpmbuild installs. Me, I build my own rpms if I have to and keep the software that I'm especially interested in as up-to-date as possible, never use RH's up2date.
To be honest, I dont like up2date and never have. I am not comfortable with using it, especially since they are no longer going to support RH 8 here soon. I do prefer to compile my own packages. I guess the reason why I was asking is because, since it was suggested to build your own RPMS on the web site, that is why I chose to do so.
Now, since there is a more recent, newer version of courier-IMAP out that I would like to install on my system, I was curious if the same manner I used before to build my packages and install would be the best route to take at this time, since I installed the original courier via RPM. I did d/l the latest courier source tarball and build my own rpm packages and everything appears to have worked ok. No errors or warnings of any sort. The only question at this time is, by upgrading/freshening the courier IMAP packages I just built, any possibility of breaking things...that is my biggest quesiton at this time.
My present Courier version is 2.2.1; I compiled it myself to my own specs. I can build rpms from my compile, if I choose. Maybe someone has 2.2.1 source or binary rpms for you - but even if you use those, unless you tell up2date to ignore your selected own stuff, if will ruin things for you at your next update. Notwithstanding - RedHat in its wisdom has decided to drop up2date for RH 8 & 9 real soon, so that problem won't exist any more for you, in a month or so.
Always good to hear. :)
You have to make a policy choice - rpms (the only way to mass-update many machines) - or source for a single or a couple of machines.
Very true. I prefer source by default, so its a matter of weighing things.
--Tonni
Thanks.
Jason