Gemfile.lock questions

Jason Guiditta jguiditt at redhat.com
Thu May 31 14:03:20 UTC 2012


On 30/05/12 22:52 -0400, Michael Orazi wrote:
>
>
>----- Original Message -----
>> On 24/04/12 21:20 +0300, Ohad Levy wrote:
>> >On 04/24/2012 04:26 AM, Jason Guiditta wrote:
>> >>
>
>Any updates?
>
>m

Phase one is complete, though I ut the initial batch of code directly
in aeolus conductor[1].  I was going to put the Ext library up on our
github incubator project[2], but realized one of my tests depends on a
specific gem library being installed (tests a certain case where the
require name doesn't match the name fo the gem).  So, I need to at
least disable that test for now before I can push it, which I will
hopefully get to today or tomorrow.  However, it is working well in
initial use, and has allowed our project to run upstream (pure ruby)
on rails 3.2, while keeping our fedora/rhel releases running on 3.0.10
(meaning we will be ready to use the newer rails the second it is
supported on those platforms).

I'll send an update when I have pushed BundlerExt to github, thanks
for the reminder.

[1] https://github.com/aeolusproject/conductor
[2] https://github.com/aeolus-incubator

-j


More information about the ruby-sig mailing list