-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/12/11 18:05, Steve Wills wrote:
>
> Finally getting back to this.
>
> Here's an updated version of the patch:
>
> http://people.freebsd.org/~swills/ruby19_and_gems_changes3.diff.txt
>
> This, along with a patch to ruby-bdb:
>
> http://people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/26/11 00:26, Stanislav Sedov wrote:
> On Wed, 25 May 2011 07:54:21 -0400
> Steve Wills mentioned:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Thanks for the feedback!
>>
>> I was attempting to do some run time testing of this an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/11 09:12, Eric wrote:
>> From: Steve Wills
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Thanks for the feedback!
>>
>> I was attempting to do some run time testing of this and stumbled upon a
>> strange issue. It seems that ev
On Wed, 25 May 2011 07:54:21 -0400
Steve Wills mentioned:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thanks for the feedback!
>
> I was attempting to do some run time testing of this and stumbled upon a
> strange issue. It seems that even without my patch (and with it too), if
> you
On 5/25/2011 4:54 AM, Steve Wills wrote:
> Thanks for the feedback!
>
> I was attempting to do some run time testing of this and stumbled upon a
> strange issue. It seems that even without my patch (and with it too), if
> you do this:
>
> cd /usr/ports/databases/ruby-bdb
> env RUBY_VER=1.9 make i
> From: Steve Wills
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thanks for the feedback!
>
> I was attempting to do some run time testing of this and stumbled upon a
> strange issue. It seems that even without my patch (and with it too), if
> you do this:
>
> cd /usr/ports/database
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the feedback!
I was attempting to do some run time testing of this and stumbled upon a
strange issue. It seems that even without my patch (and with it too), if
you do this:
cd /usr/ports/databases/ruby-bdb
env RUBY_VER=1.9 make install
on
On 05/19/11 02:02, Steve Wills wrote:
The diff, and suggested progression seem rational and right to me. I've
only read the diff though, not tried it.
> gems and rake from ports for Ruby 1.9, just like we do for 1.8. This is
> needed because some gems need the newer gems and rake.
>
> - From ther