On 28.08.2007, at 12:38, Jeff Green wrote: > Debian makes the very civillised assumption that not everyone who runs > an application needs the ability to compile the application. Now if we > can just get a nice integration between apt and gem we would have a > much > more usable and secure system.
RubyGems and APT collide here. Debian's policy is to favor APT over RubyGems, because they don't like the idea of having two package management systems. Fair enough. If you go the Debian way, you would install any gems via APT. Since not every gem (including Ferret) exists as a Debian package, your possibilities are quite limited with this approach. The alternative is to install only ruby, ruby-dev and rubygems via APT and then install gems via RubyGems. However, for gems with native extenstions, you don't have the luxury of dependecy-management. For example: if you install the RMagick gem, you need to install the ImageMagick (dev) packages via APT first. Had you installed the RMagick gem via APT, this dependency would have been installed automatically. On Debian you always need to install the development files for a package in order to compile anything against it. Development packages begin with "lib" and end with "-dev". So for MySQL and ImageMagick these are "libmysqlclient15-dev" and "libmagick9-dev", respectively. It's important to note that, in order to compile _anything_ on Debian, the gcc, make, autoconf and build-essential packages must be installed first. Cheers, Andy _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
