13 ms·

Well, I use Debian for development and production, and I would never use Debian ruby packages on production. With the Debian packages, you have no idea what ve

by andyl 14y ago

Well, I use Debian for development and production, and I would never use Debian ruby packages on production. With the Debian packages, you have no idea what version you're getting. And then gem installs can only be done by the root user, not the deploy user. What a mess. Godspeed Leader Nussbaum! I hope that your first action is to find a replacement for whoever was responsible for the debian-ruby disaster.

_delirium 14y ago
I haven't used Ruby much, but the Debian approach works well for me in Perl. I like that instead of pulling random packages off CPAN with no testing, I can depend on a Debian package of a Perl module, which is integration-tested with the rest of the distribution and release-managed, especially in terms of which other packages and versions it works with.
- kawsper 14y ago
  How do you ensure which versions of the packages that you receive? It is nice to rely on system-packages, but if you depend on certain versions of certain packages you might see problems with that approach.
  - ars 14y ago
    If you depend on certain versions of a package you have bigger problems.
    - kawsper 14y ago
      Yeah, legacy systems, you are fortunate if you don't have to deal with these.
  - deleted 14y ago
    [deleted]
alrs 14y ago
apt-get -s install ruby1.9.1-full. A simulation-only dry run that will show you exactly what is being installed.
jeltz 14y ago
I am pretty sure I have done gem installs as the current user with the Debian packages. It could be that they changed something recently though.