Hi, The change to installing rubygems --destdir doesn''t work for me. Am I missing something? I get this: fileutils.rb:243:in `mkdir'': Invalid argument - D:/src/rubyinstaller/sandbox/rubygems_mingw/D: Lars
On Sat, Jul 12, 2008 at 2:45 PM, Lars Christensen <larsch at belunktum.dk> wrote:> Hi, > > The change to installing rubygems --destdir doesn''t work for me. Am I > missing something? I get this: > > fileutils.rb:243:in `mkdir'': Invalid argument - > D:/src/rubyinstaller/sandbox/rubygems_mingw/D: >Hello Lars, We found that using --prefix only copied the binaries and the libraries of ruby outside sandbox/ruby_mingw, but the folder structure where the gems will be stored still remains inside of it. --destdir is supposed to allow packagers (in Linux) to replicate the folder structure outside the installation directory, something we have been doing manually. The thing is that parameter is broken in 1.2 and I committed a fix for it, as you can see in the changelog: http://rubygems.rubyforge.org/svn/trunk/ChangeLog Also this is the mailing list post that describe the situation: http://rubyforge.org/pipermail/rubygems-developers/2008-July/003969.html I got approval from Eric Hodel to commit the fix. The problem is yet there is no official release for 1.2.1, so I''ve been using rake CHECKOUT=1 to build from svn these components. Thankfully Ruby SVN now works, but I''ll keep my fingers crossed just in case ;-) BTW, I took a look at your fork, looks good. The only downside is the strawberry perl is huge :-P I''ve been thinking in peek the GNUwin32 guys to update their packages, but that will be silly (and will not get good reactions). The other workaround is remove the dependencies build nightware from rubyinstaller and provide (to us) pre-packaged binary versions of OpenSSL, Readline, Iconv, Gettext, etc. Anyway, open to suggestions.> Lars >Thank you Lars for pointing this down. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams
On Sat, 12 Jul 2008, Luis Lavena wrote:> On Sat, Jul 12, 2008 at 2:45 PM, Lars Christensen <larsch at belunktum.dk> wrote: >> The change to installing rubygems --destdir doesn''t work for me. Am I >> missing something? > > --destdir is supposed to allow packagers (in Linux) to replicate the > folder structure outside the installation directory, something we have > been doing manually.Ruby''s configure is called with --prefix. Could change be changed to --destdir?> The problem is yet there is no official release for 1.2.1, so I''ve been > using rake CHECKOUT=1 to build from svn these components.Thanks, I''ll use that until rubygems gets released.> BTW, I took a look at your fork, looks good. The only downside is the > strawberry perl is huge :-PYes, its far from optimal. Suggestions welcome :)> I''ve been thinking in peek the GNUwin32 guys to update their packages, > but that will be silly (and will not get good reactions). > > The other workaround is remove the dependencies build nightware from > rubyinstaller and provide (to us) pre-packaged binary versions of > OpenSSL, Readline, Iconv, Gettext, etc. > > Anyway, open to suggestions.I personal prefer to keep the option to build everything from sources & official binaries (gnuwin32 permitted). This way, if someone wants to fix/modify/upgrade a dependency, its completely transparent how rubyinstaller generates it from its official source. It would be possible to give the user an option of using prebuilt packages, for example by specifying "rake USEPREBUILT=1". Lars
On Sat, Jul 12, 2008 at 7:54 PM, Lars Christensen <larsch at belunktum.dk> wrote:> > On Sat, 12 Jul 2008, Luis Lavena wrote: > >> On Sat, Jul 12, 2008 at 2:45 PM, Lars Christensen <larsch at belunktum.dk> >> wrote: >>> >>> The change to installing rubygems --destdir doesn''t work for me. Am I >>> missing something? >> >> --destdir is supposed to allow packagers (in Linux) to replicate the >> folder structure outside the installation directory, something we have >> been doing manually. > > Ruby''s configure is called with --prefix. Could change be changed to > --destdir? >There is no --destdir for Ruby, only for RubyGems.>> The problem is yet there is no official release for 1.2.1, so I''ve been >> using rake CHECKOUT=1 to build from svn these components. > > Thanks, I''ll use that until rubygems gets released. >Keep in mind that you will require to remove the folders from ruby_mingw (lib/ruby/1.8/gems/*) since they belong to rubygems_mingw instead>> BTW, I took a look at your fork, looks good. The only downside is the >> strawberry perl is huge :-P > > Yes, its far from optimal. Suggestions welcome :) >I think I found a workaround using msys-perl and some tweaks to openssl generated makefile. Will test it a bit more and share that with you.>> I''ve been thinking in peek the GNUwin32 guys to update their packages, >> but that will be silly (and will not get good reactions). >> >> The other workaround is remove the dependencies build nightware from >> rubyinstaller and provide (to us) pre-packaged binary versions of >> OpenSSL, Readline, Iconv, Gettext, etc. >> >> Anyway, open to suggestions. > > I personal prefer to keep the option to build everything from sources & > official binaries (gnuwin32 permitted). This way, if someone wants to > fix/modify/upgrade a dependency, its completely transparent how > rubyinstaller generates it from its official source. > > It would be possible to give the user an option of using prebuilt packages, > for example by specifying "rake USEPREBUILT=1". >In any case, the rubyinstaller is ideally target to One-Click Installer developers and not end users, so the usage of pre-build vs. source is non-critical.> Lars >-- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams