Hmmm, hadn't thought of RPM. But I would like a direct answer to my question, which was: Can I just tar up everything in a dovecot-only prefix directory (defined in the invocation of configure) when the make and make install is done, and then untar/extract it in a directory of the same name over on another machine with the same OS, patches and OpenSSL? Are there Dovecot dependencies outside prefix directory.
My OS is AIXV5.3 maintenance/tech level 4. There is no distro RPMs for same, so I am building it myself.
Lior wrote:
The problem you are describing is solved with tools like RPM and DEB.
You can install/remove an entire package with a single command, you can verify the installation with a single command, you can safetly upgrade with a single command, and safetly revert to an older version with a single command.
These tools allow you to find out exactly which file belongs to what package, and they prevent conflicting files from two different packages from being installed. Not to mention (almost) automatic (at least on debian) dependency resolving for packages.
If you're using Debian, you can just "apt-get install dovecot-imap dovecot-pop", and have the dpkg handle all of the issues you mentioned. If you're using an RPM based distro- try yum or apt-rpm.
Lior
Timothy White wrote:
If you're using Debian, you can just "apt-get install dovecot-imap dovecot-pop", and have the dpkg handle all of the issues you mentioned. If you're using an RPM based distro- try yum or apt-rpm.
And there is nothing stopping you making a deb package, from a newer version of dovecot, that Debian has, AND, duplicating the server, so you can do a test upgrade... Of course, with any upgrade, someone will notice something ;-)
Tim
Linux Counter user #273956
--
Stewart Dean, Unix System Admin, Henderson Computer Resources
Center of Bard College, Annandale-on-Hudson, New York 12504
sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035