Sam Varshavchik <mrs...@courier-mta.com> writes:
Lloyd Zusman writes:
I'm about to freshly install Courier on a new machine, and I want to
make sure that I understand the proper sequence of events. This machine
is currently using sendmail, and I want to keep that program up and
running for as long as possible before switching over to Courier.
To the best of my understanding, this should be the scenario. If any
of you see any flaws in this, could you let me know? Thanks.
1. Use rpmbuild to build a binary rpm for courier-authlib.
2. Do an rpm install of courier-authlib.
3. Use rpmbuld to build a binary rpm for courier.
4. Shut down and disable sendmail.
5. Do an rpm install of courier.
6. Check the courier-authlib and courier configurations, and
make any necessary changes.
7. Start up courier.
A question: could I switch the order of steps 2 and 3, or is there some
reason for why I should install courier-authlib before building the
courier binary rpm?
Courier requires courier-authlib to be already installed, before it can
build.
Specifically, you need courier-authlib-devel installed.
OK. Thanks.