On Wed, Aug 4, 2010 at 13:23, Jay G. Scott <g...@arlut.utexas.edu> wrote: > > what's the deal w/ no configure script? > > you do know that you DON'T NEED autoconf/automake to install, right? > they're not hiding behind that old dodge, are they? i'm so sick of > that. > > if i supply a configure script, will you guys use it? > > every time i try to go to a newer version of postfix, the > installation overwrites the previous version. and that > interferes w/ my system documentation. w/ a configure script > i can install into a safe, stub directory w/o clobbering the > existing files. then i can do a proper migration.
Install on a new migration machine on which you can do proper testing before making the switch. Be sure this new migration machine also has the latest version of your favorite OS, as well as latest version of related software (your IMAP server, your DB engine, etc). Move test domains to this server first and make sure it works. Then somewhat before the appointed time, move all the data to the new machine. Then synchronize it one more time at the last moment and stop email on the old machine. Bring up email on the new machine and run all your tests again with the primary domain(s). If something doesn't work, shutdown and move back. Whether you "move" by IP address or DNS changes or swapping hard drives is your choice. There are a number of ways to do this. But I don't know anyone who would just up and install a new software version on top of an existing server. So I would not imagine Postfix making any effort to support such a thing. I could be wrong, but I wouldn't make any effort to have a software package support it. I've done the two machine migration approach for 30 years. But if you really insist on doing it all on one machine, might I suggest a chroot tree copy, or a virtual machine? -- sHiFt HaPpEnS!
