On Wed, Oct 29, 2008 at 5:13 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> If you're using the API to install gems, you get the benefit of the
> :install_dir option, so there's no need to set any environment variables.
> If you're writing a script that drives bin/gem, you can either set an
> enviro
On Oct 27, 2008, at 12:22 PM, Chad Woolley wrote:
On Sun, Oct 26, 2008 at 10:14 PM, Eric Hodel <[EMAIL PROTECTED]>
wrote:
On Oct 25, 2008, at 20:17 PM, Chad Woolley wrote:
Then will there be any way to configure all gems to be installed
and loaded from ~/.gem, without any root access required
On Sun, Oct 26, 2008 at 10:14 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> On Oct 25, 2008, at 20:17 PM, Chad Woolley wrote:
>
>> Then will there be any way to configure all gems to be installed and
>> loaded from ~/.gem, without any root access required (as long as
>> ~/.gem/.../bin is on path)?
>
On Oct 25, 2008, at 20:17 PM, Chad Woolley wrote:
On Sat, Oct 25, 2008 at 2:37 PM, Eric Hodel <[EMAIL PROTECTED]>
wrote:
I may have to remove the :gemhome: and :gempath: in ~/.gemrc, since
it is very difficult to reproduce the functionality in
gem_prelude.rb for 1.9.
Then will there be any
On Sat, Oct 25, 2008 at 2:37 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> I may have to remove the :gemhome: and :gempath: in ~/.gemrc, since it is
> very difficult to reproduce the functionality in gem_prelude.rb for 1.9.
>
Then will there be any way to configure all gems to be installed and load
On Oct 22, 2008, at 14:02 PM, Chad Woolley wrote:
On Tue, Oct 21, 2008 at 11:06 AM, Chad Woolley <[EMAIL PROTECTED]
> wrote:
I'm getting some functional test failures in the GemInstaller suite
on OSX (not linux). I'll try to look into it tonight.
These test failures go away if I comment out
On Tue, Oct 21, 2008 at 11:06 AM, Chad Woolley <[EMAIL PROTECTED]>wrote:
> I'm getting some functional test failures in the GemInstaller suite on OSX
> (not linux). I'll try to look into it tonight.
>
These test failures go away if I comment out my ~/.gemrc, where I've
overridden gemhome and gem
On Oct 21, 2008, at 13:36 PM, Berger, Daniel wrote:
Are you making minitest a requirement even for 1.8.x? That's how it
seems to be now:
Yes.
How will that work in practice if I do "gem update --system"? Will
it go
out and automatically grab minitest for me? Or is it pre-bundled
somehow? J
On Tue, Oct 21, 2008 at 6:07 PM, Berger, Daniel <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
>> >>
>> >> Gem::location_of_caller is insufficient for windows paths :/
>> >
>> > How does this look?
>> >
>> > C:\>diff -u rubygems.orig rubygems.rb
>> > --- rubygems.orig Mon Sep 29 08:01:06 2008
>> > +
Hi,
> >>
> >> Gem::location_of_caller is insufficient for windows paths :/
> >
> > How does this look?
> >
> > C:\>diff -u rubygems.orig rubygems.rb
> > --- rubygems.orig Mon Sep 29 08:01:06 2008
> > +++ rubygems.rb Tue Oct 21 14:29:27 2008
> > @@ -479,8 +479,9 @@
> > # The file name an
On Tue, Oct 21, 2008 at 5:36 PM, Berger, Daniel <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
>> >> Silencing the PATH warning for unpack Fixes for
>> Gem.inflate, deflate,
>> >> etc.
>> >> Switched to MiniTest for 1.9 compatibility Gem.dir reads
>> >
>> > Are you making minitest a requirement even for 1
On Tue, Oct 21, 2008 at 5:08 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> On Oct 21, 2008, at 08:53 AM, Berger, Daniel wrote:
>>>
>>> -Original Message-
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] On Behalf
>>> Of Eric Hodel
>>> Sent: Monday, October 20, 2008 7:38 PM
>>> To: ru
Hi,
> >> Silencing the PATH warning for unpack Fixes for
> Gem.inflate, deflate,
> >> etc.
> >> Switched to MiniTest for 1.9 compatibility Gem.dir reads
> >
> > Are you making minitest a requirement even for 1.8.x? That's how it
> > seems to be now:
>
> Yes.
How will that work in practice
On Oct 20, 2008, at 20:25 PM, James M. Lawrence wrote:
On Mon, Oct 20, 2008 at 9:37 PM, Eric Hodel <[EMAIL PROTECTED]>
wrote:
I will be including the current trunk on Thursday in Ruby for the
upcoming
1.9.1. Shortly afterward I will release RubyGems 1.3.1.
Would it be possible to apply thi
On Oct 21, 2008, at 08:53 AM, Berger, Daniel wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Eric Hodel
Sent: Monday, October 20, 2008 7:38 PM
To: rubygems-developers@rubyforge.org
Subject: [Rubygems-developers] Please test for a 1.3.1
I will be i
On Mon, Oct 20, 2008 at 6:37 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> I will be including the current trunk on Thursday in Ruby for the upcoming
> 1.9.1. Shortly afterward I will release RubyGems 1.3.1. There are only a
> few bug fixes:
>
I'm getting some functional test failures in the GemI
On Tue, Oct 21, 2008 at 12:53 PM, Berger, Daniel
<[EMAIL PROTECTED]> wrote:
> > -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf
>> Of Eric Hodel
>> Sent: Monday, October 20, 2008 7:38 PM
>> To: rubygems-developers@rubyforge.org
>> Subject: [Rubygems-dev
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Eric Hodel
> Sent: Monday, October 20, 2008 7:38 PM
> To: rubygems-developers@rubyforge.org
> Subject: [Rubygems-developers] Please test for a 1.3.1
>
> I will be including the current trunk on Thu
On Mon, Oct 20, 2008 at 9:37 PM, Eric Hodel <[EMAIL PROTECTED]> wrote:
> I will be including the current trunk on Thursday in Ruby for the upcoming
> 1.9.1. Shortly afterward I will release RubyGems 1.3.1.
Would it be possible to apply this tiny patch to fix #20801
% ruby -r rubygems -e 'p "foo"
19 matches
Mail list logo
