On Sun, Jan 20, 2013 at 4:12 PM, Clint Pachl <pa...@ecentryx.com> wrote:
> Can't Sinatra be managed in the same way Jeremy proposes for Rails? I.e., > remove it from the OpenBSD tree and manage it via gem. > > I've been using gem to manage Ruby gems (sinatra, tilt, rack, > rack-protection, erubis, etc.) directly and this seems to work. No need to > duplicate the efforts in the OpenBSD package system. > > The only "management issue" I face is determining whether I have to update > a ruby gem via pkg_add or gem. I've simply configured my ruby/gem software > to source/install from/to /usr/local/rubygems. This creates separation > between the pkg_add and gem systems so I don't cause any unforeseen > problems. It's been working for me for almost a year now. However, I think > it would be safe to install all ruby gems in OpenBSD's location: > /usr/local/lib/ruby/gems. > > I started doing this ever since Mr. Evans proposed chopping non-compiled > ruby gems from the OpenBSD tree. I kind of like the idea. You are correct, it's possible to handle it the same way. The problem is not nearly as bad as it is with Rails, since Sinatra is small and has few dependencies. Sinatra can't currently be removed as a couple of ports depend on it (resque and ronn), so those ports would have to be removed first. Thanks, Jeremy
