Em 26-04-2011 04:50, Marius Mårnes Mathiesen escreveu:
On Mon, Apr 25, 2011 at 3:21 PM, Rodrigo Rosenfeld Rosas
<[email protected] <mailto:[email protected]>> wrote:
Hi, I'm trying to write a good Chef recipe that could install
Gitorious as fast as possible.
Great stuff!
It would be good if I could use a fresh Debian installation with
its own Ruby, but it means it would me much easier if Gitorious
supported current RubyGems. In my current chef recipe for
Gitorious, I use to have RVM REE with RubyGems 1.5.2 ("rvm rubgems
1.5.2"), but this command is broken at the moment, and I'm talking
with Wayne about it... But it would be much better if I didn't
need RVM and could use Ruby from Debian with no extra step for
downgrading RubyGems or patching Gitorious...
Would it be possible to support newer RubyGems?
I suppose so, shouldn't be all that much work?
Actually, since a while ago, there is already a working recipe for Chef:
http://rosenfeld.heroku.com/en/articles/2011-03-06-installing-gitorious-has-never-been-so-easy
It is working (last time I tested was yesterday), but I would like it to
be faster... Currently the recipe uses RVM but I would like to try it
with native Ruby from Debian, which could speed up the installation
procedure.
In RVM, I can do "rvm rubygems 1.5.2" and it will install the 1.5.2
RubyGems for me. But writing this manually in the recipe for Ruby
distributed in Debian seems like a lot of work. I would rather prefer
Gitorious to support newer RubyGems...
That is why I'm asking for merging the solution provided by Johansen,
adding the following to config/environment.rb:
http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own_server
if Gem::VERSION >= "1.3.6"
module Rails
class GemDependency
def requirement
r = super(r == Gem::Requirement.default) ? nil : r
end
end
end
end
It would be much better to upgrade to a newer Rails, but this would help
for now...
Did I understand correctly your question?
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
