Sam Varshavchik wrote:
me...@bauchladen.at writes:
Now my question is: If I start moving from RPM built packages to
tarball compiled stuff where do I get the dependencies information
from? How do I know which libraries, their versions and
other software
the given release of courier needs to build or at runtime?
If I have
missed something in TFManual then I beg for a hint and your pardon.
INSTALL tells you what stuff needs to be installed first.
From there, you
figure out the actual libraries.
Another option you have is to build your own RPMs. The document at
http://www.courier-mta.org/status.html states:
Building RPMs
You can build binary Courier RPMs directly from the tarball, using RPM
version 4.0.2 or higher. For example:
. . .
As you can see, you can build your own RPMs as new versions of Courier
are released. It is really not hard to do. And the RPM building
process will yell at you for any failed dependencies, and you can then
research the library specified and so some research to see what package
you need to install to satisfy such dependencies.
If you are going to go down this road, do not forget that you cannot
build the RPMs as root.
HTH,
6 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: courier depen...
