Hello List, I''ve committed a patch to the rakefile (and the utils) that allow inline patching of files like the case we are dealing right now. Also, I''ll like to point that Ruby Core developers fixed the issue we found in the stable and trunk branches, so these problems will go away in future releases. Curt, as you said before, the building process is too brittle and it requires more testing. I guess that RubyInstaller 3.0 (the successor after this) will be more modular allowing us extending and removing parts of it (like which version of ruby ship). All this process allow me gather information :-) Good weekend everybody. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
On 10/13/07, Luis Lavena <luislavena at gmail.com> wrote:> > Hello List, > > I''ve committed a patch to the rakefile (and the utils) that allow > inline patching of files like the case we are dealing right now.Excellent! I''ll update my copy and do a build. If everything goes alright we can put out a release candidate. Also, I''ll like to point that Ruby Core developers fixed the issue we> found in the stable and trunk branches, so these problems will go away > in future releases. > > Curt, as you said before, the building process is too brittle and it > requires more testing. > > I guess that RubyInstaller 3.0 (the successor after this) will be more > modular allowing us extending and removing parts of it (like which > version of ruby ship).Yes, yes, yes! I knew we''d have to deal with the compiler issue sometime, and figured that would be a good time to improve the build process. Curt All this process allow me gather information :-)> > Good weekend everybody. > > -- > Luis Lavena > Multimedia systems > - > Leaders are made, they are not born. They are made by hard effort, > which is the price which all of us must pay to achieve any goal that > is worthwhile. > Vince Lombardi > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/e2e08aa3/attachment.html
Also, I''m thinking that we might want to wait for RubyGems 0.9.5 before doing a final OCI release (it''d be nice to have the latest RubyGems release in there). Curt On 10/15/07, Curt Hibbs <curt.hibbs at gmail.com> wrote:> > On 10/13/07, Luis Lavena <luislavena at gmail.com> wrote: > > > > Hello List, > > > > I''ve committed a patch to the rakefile (and the utils) that allow > > inline patching of files like the case we are dealing right now. > > > Excellent! I''ll update my copy and do a build. If everything goes alright > we can put out a release candidate. > > Also, I''ll like to point that Ruby Core developers fixed the issue we > > found in the stable and trunk branches, so these problems will go away > > in future releases. > > > > Curt, as you said before, the building process is too brittle and it > > requires more testing. > > > > I guess that RubyInstaller 3.0 (the successor after this) will be more > > modular allowing us extending and removing parts of it (like which > > version of ruby ship). > > > Yes, yes, yes! > > I knew we''d have to deal with the compiler issue sometime, and figured > that would be a good time to improve the build process. > > Curt > > All this process allow me gather information :-) > > > > Good weekend everybody. > > > > -- > > Luis Lavena > > Multimedia systems > > - > > Leaders are made, they are not born. They are made by hard effort, > > which is the price which all of us must pay to achieve any goal that > > is worthwhile. > > Vince Lombardi > > _______________________________________________ > > Rubyinstaller-devel mailing list > > Rubyinstaller-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/9bee1a90/attachment.html
On 10/15/07, Curt Hibbs <curt.hibbs at gmail.com> wrote:> Also, I''m thinking that we might want to wait for RubyGems 0.9.5 before > doing a final OCI release (it''d be nice to have the latest RubyGems release > in there). >Yes, that''s why I''m beta-testing and nuking my ruby installation here trying the new platform specs and building gems with it. We will require removing the patching of .cmd scripts for rubygems, since that method brakes IDE integrations like NetBeans and Aptana. (they are looking for "gem" and not gem.cmd). -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi
On 10/15/07, Luis Lavena <luislavena at gmail.com> wrote:> > > We will require removing the patching of .cmd scripts for rubygems, > since that method brakes IDE integrations like NetBeans and Aptana. > (they are looking for "gem" and not gem.cmd).I already stopped doing that because of the IDE integration problem. The last release of OCI uses path-independent bat files (not cmd files) and on the original ruby files (without extentions). So, for example, in OCI 1/8/6-25 you''ll find "gem" and "gem.bat". Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20071015/e311dc91/attachment.html
On 10/15/07, Curt Hibbs <curt.hibbs at gmail.com> wrote:> On 10/15/07, Luis Lavena <luislavena at gmail.com> wrote: > > > > We will require removing the patching of .cmd scripts for rubygems, > > since that method brakes IDE integrations like NetBeans and Aptana. > > (they are looking for "gem" and not gem.cmd). > > I already stopped doing that because of the IDE integration problem. The > last release of OCI uses path-independent bat files (not cmd files) and on > the original ruby files (without extentions). So, for example, in OCI > 1/8/6-25 you''ll find "gem" and " gem.bat". >Great, I missed that part :-P Anyway, hope next rubygems sport a patch for the windows script stubs [1]. Let me know if ruby-odbc is ok and else is broken ;-) [1] http://rubyforge.org/tracker/index.php?func=detail&aid=14725&group_id=126&atid=577 -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi