Re:Giving up on Ruby packaging
by erikpukinskis on Monday January 03, 2011 @04:35AM
(#2062684)
I don't think that really makes sense. I think the sysadmin should instead have to do:
apt-get install rubygems
gem install redmine
I know it's two steps and they have to understand the dependency, but the truth is everyone in the Ruby world kind of assumes you're using Rubygems, and repackaging things from one packaging format to another just seems like it's asking for trouble.Sysadmins can learn that if they want something from the ruby world they have to install rubygems.
Re:Giving up on Ruby packaging
by regularfry on Monday January 03, 2011 @05:33AM
(#2062760)
That way lies madness. Consider:
* "Sysadmins can learn that if they want something from the Python world they have to install pip."
* "Sysadmins can learn that if they want something from the Lisp world they have to install clbuild."
* "Sysadmins can learn that if they want something from the Lua world they have to install luarocks."
* "Sysadmins can learn that if they want something from the PHP world they have to install PEAR."
* "Sysadmins can learn that if they want something from the Perl world they have to install CPAN."
* "Sysadmins can learn that if they want something from the Haskell world they have to install cabal."
* "Sysadmins can learn that if they want something from the O'Caml world they have to install godi."
Re:Giving up on Ruby packaging
by halostatue on Monday January 03, 2011 @07:34AM
(#2062932)
Why can't "apt-get install redmine" do what you suggest behind the scenes?
One use case would be if someone, say a sysadmin, wants a good bug tracking system for internal use at their company.
Fetches Rails, Ruby and so on, and sets it up in a default, reasonably secure way (as far as I know, I haven't the Debian version myself).That sort of thing is pretty commonplace with PHP web applications under Debian and Ubuntu. Granted, if you're going to hack on and modify the application in question, yeah, you may want to get it and install it yourself, but when things work well, a good packaging system lets you install and work with code that perhaps you do not know intimately.
I think you're making the mistake of viewing the world exclusively from the point of view of a Ruby developer. What would happen if you had to deal with different systems to install, maintain and upgrade the Linux kernel, Apache, Postgres, Sqlite, Ruby, GCC, Perl, Python, Gnome, and various submodules used by them? There are times when it's necessary to install your own version of something, but it's awfully, awfully nice that you can "choose your battles", and really only do that with stuff you care about and follow closely.
Sounds like Linux in the days when you installed Slackware and then just upgraded stuff by randomly recompiling bits and pieces every now and then.
BTW, I would hope that we could skip any "angry disagreements" here. Passion will do more than suffice!