> Sam Varshavchik wrote: > > [EMAIL PROTECTED] 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, David Gomillion ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
