Has anyone tried deploying Rails as rpms instead of via gems?
Gems are great for installing rails. Rails is updated too often for any traditional packaging system to keep up. On Fri, 18 Mar 2005 09:24:55 -0800, Miles Egan <milesegan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Has anyone tried deploying Rails as rpms instead of via gems? > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Tobi http://www.snowdevil.ca - Snowboards that don''t suck http://www.hieraki.org - Open source book authoring http://blog.leetsoft.com - Technical weblog
Tobias Luetke wrote:>Gems are great for installing rails. Rails is updated too often for >any traditional packaging system to keep up. > >Now now, let''s not be too rash :P http://packages.debian.org/rails Rails might not be ready to be released with Sarge (rails 1.0), but the version in Sid will keep up with upstream :) - Adam
On Fri, 18 Mar 2005 12:26:14 -0500, Tobias Luetke <tobias.luetke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Gems are great for installing rails. Rails is updated too often for > any traditional packaging system to keep up.This is fine if you''re the developer, system administrator and support team all in one... Larger organizations may balk at something outside of the standard packaging system though. Its not that much effort to package it up into RPMs, you just need some helper scripts to operate on .gem files, that get included into the SRPM. A few minutes after the 0.10.1 release it was already part of our in-house web server installation .ISO image :) Leon