Rubyinstaller devel - Jun 2008 - Ruby 1.86. p230 and RubyGems 1.2.0

With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
upcoming RubyGems 1.2.0[2] release, I''ve worked some on updating
installer3.  The changes are in my github repo[3]

Below are a list of issues that I have.  I''d like some feedback from
anyone out there that''s paying attention ;-D  Any ways to improve what
I''m doing?  Anything I''m missing?

Iconv issue

	Which package do we need to switch to?
	
Wix issues

	Need to write paraffin tasks

		The steps Luis used to generate the wxs frgaments are documented in
the comments of wix.rake.  I just haven''t gotten around to it yet.

	Paraffin updates, but `rake package` fails

		I can update the .wxs files using the steps Luis laid out, but wix
errors out when it''s run.  Not sure what''s going on here.
light.exe is
throwing some odd errors [4].

 	Need a gui

		Once wxs fragments issue gets straightened out, we still need to
build a gui for the installer

Mingw, Msys issues

	Needs wxs files generated
 	
 	Need a task to add batch files to %rubypath%\bin
 	
		make.bat, gcc.bat, sh.bat
  	
[1] 
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
[2]  http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
[3]  http://github.com/vertiginous/rubyinstaller
[4] http://pastie.org/219031

Thanks,

Gordon

> Iconv issue
>
>        Which package do we need to switch to?
Apparently it''s non-trivial, but you can compile your own DLL with
mingw.
http://wiki.rubyonrails.org/rails/pages/Win32MingwInstall [sorry it''s
messy].

Are you planning on releasing mingw or win32?
GL!
-R

On Fri, Jun 20, 2008 at 8:48 PM, Roger Pack <rogerpack2005 at gmail.com>
wrote:
>> Iconv issue
>>
>>        Which package do we need to switch to?
> Apparently it''s non-trivial, but you can compile your own DLL with
mingw.
> http://wiki.rubyonrails.org/rails/pages/Win32MingwInstall [sorry
it''s messy].
>
Yeah, and confusing! :-P
> Are you planning on releasing mingw or win32?
Dunno what you mean... releasing what?

-- 
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 Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at
gmail.com> wrote:
> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
> upcoming RubyGems 1.2.0[2] release, I''ve worked some on updating
> installer3.  The changes are in my github repo[3]
>
> Below are a list of issues that I have.  I''d like some feedback
from
> anyone out there that''s paying attention ;-D  Any ways to improve
what
> I''m doing?  Anything I''m missing?
>
> Iconv issue
>
>        Which package do we need to switch to?
>
We should revert from win-iconv to gnuwin32 iconv version:

http://gnuwin32.sourceforge.net/packages/libiconv.htm

We need binaries and dependencies.
> Wix issues
>
>        Need to write paraffin tasks
>
>                The steps Luis used to generate the wxs frgaments are
documented in
> the comments of wix.rake.  I just haven''t gotten around to it yet.
>
>        Paraffin updates, but `rake package` fails
>
>                I can update the .wxs files using the steps Luis laid out,
but wix
> errors out when it''s run.  Not sure what''s going on here.
light.exe is
> throwing some odd errors [4].
>
I''ll verify it but there is no need to copy the wxs fragments into
sandbox to work. I used the relative references as workaround.
>        Need a gui
>
>                Once wxs fragments issue gets straightened out, we still
need to
> build a gui for the installer
>
Yeah, didn''t had time to work on that yet.
> Mingw, Msys issues
>
>        Needs wxs files generated
>
Yes, each one for each gcc package, maybe we would handle those
manually based on the version, but will not be part of the automated
process (dunno yet, we need to talk a bit about it).
>        Need a task to add batch files to %rubypath%\bin
>
>                make.bat, gcc.bat, sh.bat
>
These files should be fit better into "resources", I''ll work
on that
after the MinGW stuff.
> [1] 
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
> [2] 
http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
> [3]  http://github.com/vertiginous/rubyinstaller
> [4] http://pastie.org/219031
>
> Thanks,
>
Thanks to you Gordon, I''ll check all that today!
(still owe you a ruby bugfix). ;-)
-- 
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 Fri, Jun 20, 2008 at 2:18 PM, Luis Lavena <luislavena at gmail.com>
wrote:
> On Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at
gmail.com> wrote:
>> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>> upcoming RubyGems 1.2.0[2] release, I''ve worked some on
updating
>> installer3.  The changes are in my github repo[3]
>>
>> Below are a list of issues that I have.  I''d like some
feedback from
>> anyone out there that''s paying attention ;-D  Any ways to
improve what
>> I''m doing?  Anything I''m missing?
>>
>> Iconv issue
>>
>>        Which package do we need to switch to?
>>
>
> We should revert from win-iconv to gnuwin32 iconv version:
>
> http://gnuwin32.sourceforge.net/packages/libiconv.htm
>
> We need binaries and dependencies.
I''m updating this now.
>
>> Wix issues
>>
>>        Need to write paraffin tasks
>>
>>                The steps Luis used to generate the wxs frgaments are
documented in
>> the comments of wix.rake.  I just haven''t gotten around to it
yet.
>>
>>        Paraffin updates, but `rake package` fails
>>
>>                I can update the .wxs files using the steps Luis laid
out, but wix
>> errors out when it''s run.  Not sure what''s going on
here. light.exe is
>> throwing some odd errors [4].
>>
>
> I''ll verify it but there is no need to copy the wxs fragments into
> sandbox to work. I used the relative references as workaround.
>
I did this so that people could hack on the wxs file and still have
the original, but there are two problems with this. First, that''s what
a VCS is for, and second, the rake package task overwrites them with
the original everytime anyway.  I will fix.
>>        Need a gui
>>
>>                Once wxs fragments issue gets straightened out, we still
need to
>> build a gui for the installer
>>
>
> Yeah, didn''t had time to work on that yet.
Yeah, neither did I ;-)  Just trying to keep track of what''s left to
do.
>
>> Mingw, Msys issues
>>
>>        Needs wxs files generated
>>
>
> Yes, each one for each gcc package, maybe we would handle those
> manually based on the version, but will not be part of the automated
> process (dunno yet, we need to talk a bit about it).
>
>>        Need a task to add batch files to %rubypath%\bin
>>
>>                make.bat, gcc.bat, sh.bat
>>
>
> These files should be fit better into "resources", I''ll
work on that
> after the MinGW stuff.
I''m just trying to think through the process of how these scripts
would get packaged.  I''m thinking something similar to the way you
have rubygems set up as fragment (is that the correct term?).

>
>> [1] 
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
>> [2] 
http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
>> [3]  http://github.com/vertiginous/rubyinstaller
>> [4] http://pastie.org/219031
>>
>> Thanks,
>>
>
> Thanks to you Gordon, I''ll check all that today!
> (still owe you a ruby bugfix). ;-)
> --
> 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
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

Yeah I left it messy since installer3 came out so nobody needed it anymore :D
>> Are you planning on releasing mingw or win32?
>
> Dunno what you mean... releasing what?
My question is if this plans to be an "official" mingw release.  I
guess now is as good a time as any.  Maybe warn people that it may not
be compatible with precompiled existing win32 gems [like if they run
gem install rmagick]?
>With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>upcoming RubyGems 1.2.0[2] release, I''ve worked some on updating
>installer3.  The changes are in my github repo[3]
Or whether Gordon was referring to releasing an updated OCI VC6
distro.  Now that I look at it, since he mentioned updating
installer3, I assume it''s for mingw only?

Thanks!
-R

On Fri, Jun 20, 2008 at 10:23 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> Yeah I left it messy since installer3 came out so nobody needed it anymore
:D
>
>>> Are you planning on releasing mingw or win32?
>>
>> Dunno what you mean... releasing what?
>
> My question is if this plans to be an "official" mingw release. 
I
> guess now is as good a time as any.  Maybe warn people that it may not
> be compatible with precompiled existing win32 gems [like if they run
> gem install rmagick]?
>
Dunno if is the "official mingw" release. but it will be the One-Click
Installer for Windows "official" version, at least supported by me :-P

There is a clear difference between MinGW and VC6 builds, and I
contribute to make it more clear in latest RubyGems.

So if a binary for RMagick is build with VC6 (mswin32 as platform)
will not be automatically installed by RubyGems, you will require
manual install.

For those users that manually try it, we can''t do anything more than
say "that wouldn''t work".
>>With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>>upcoming RubyGems 1.2.0[2] release, I''ve worked some on
updating
>>installer3.  The changes are in my github repo[3]
>
> Or whether Gordon was referring to releasing an updated OCI VC6
> distro.  Now that I look at it, since he mentioned updating
> installer3, I assume it''s for mingw only?
>
installer2 is what is now OCI, the latest release is 186-26 which is 1.8.6-p114

Even Ruby-core released p230 I''ll not update installer2 since there is
no testing in place and all the extension and gems bundled must be
verified for compatibility.

installer3 is the sandbox for development and creation of the new
One-Click Installer (I should put this on my signature).

So most of the work is right now on installer3 (named rubyinstaller on
github, like the project on rubyforge).

Right now we need to get a UI for the installer, to offer the less
options possible to install the Runtime (Ruby+RubyGems) packages.

If you have some free time, feel free to fork the rubyinstaller
repository at github (like gordon did) and when you''re done with your
fixes, improvements or ideas, just send me a pull request! :-)
> Thanks!
Thanks to you, have a nice weekend!
-- 
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 Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at
gmail.com> wrote:
> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
> upcoming RubyGems 1.2.0[2] release, I''ve worked some on updating
> installer3.  The changes are in my github repo[3]
>
> Below are a list of issues that I have.  I''d like some feedback
from
> anyone out there that''s paying attention ;-D  Any ways to improve
what
> I''m doing?  Anything I''m missing?
>
I did a test on patchelevel 230 and found a series of errors that
wasn''t present before.

I sent a mail to ruby-core ([ruby-core:17364]):

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/17364

Basically Drb test or Drb itself is broken in 230, so I wouldn''t
recommend we move forward to that version until heard back from
ruby-core.

Regarding the other stuff I''m about to run RubySpecs for Iconv,
Readline and that and see how "compatible" we are right now.

Good weekend everybody!
-- 
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