Yeah, it's a PITA all right. You could download a project, and it could list a dozen library dependencies in a text file. So now you have to spend hours searching, downloading, reading manuals and compiling libraries (not to mention having to download any extra dependencies for those libs as well, and any tools used in the building process), and finally configuring the app to use the compiled libraries. And when the libs won't compile.. bleh! It's typical for many open-source C apps that I've tried compiling.
On 12/13/10, Ary Borenszweig <[email protected]> wrote: > Deploying a Ruby on Rails 2 application is like this: > > git clone ... (or hg pull ... or whatever you use) > rake gems:install (this installs all the libraries your project depend on) > rake db:create > rake db:migrate > rake db:seed > > Very, very convenient. Otherwise you have to download the jars in you > server, or > commit them to your source control which is pretty heavy. > > In D, Java, C#, etc., it's a PITA, specially when your app depends on a > specific > version of a library. >
