6 messages in net.sourceforge.lists.courier-users[courier-users] courier dependencies
FromSent OnAttachments
Warren KonkelJul 29, 2004 7:07 am 
Sam VarshavchikJul 29, 2004 3:34 pm 
me...@bauchladen.atJul 30, 2004 12:27 am 
m...@rtij.nlJul 30, 2004 1:38 am 
Sam VarshavchikJul 30, 2004 4:10 am 
David GomillionJul 30, 2004 5:56 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] courier dependenciesActions...
From:me...@bauchladen.at (me@bauchladen.at)
Date:Jul 30, 2004 12:27:49 am
List:net.sourceforge.lists.courier-users

Hello all again!

Please don't shoot for I am going to ask a question that may seem very general, even off topic. I think it's ok to ask though for it is - in this case - very much about courier. Being a newby I heavily rely on the RPM systems the distros i use provide. It currently being Debian the apt-get and dpkg systems take the task of meeting dependencies off my hands. Even when I am (trying to) building courier I run "apt-get build-dep courier" and this puts about 60MB of stuff I didn't even know existed on my system so that i can build the tarball.

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.

Michael