>Hi Curt,
>
>Thanks for the package. I guess it's very convenient for
Microsoft users.
>
>Just a question... do you plan to provide Ruby/GTK2 some day? GTK2
>works great on Windows and I believe it would be interesting to ship
>Ruby bindings for it, since you already deliver FOX bindings.
>
>(so there is no jalous
>
on the lines of the hread, I think the best thing would be to package
up all the ruby-gnome2 stuff that works on windows in some gems, and
maybe provide a choice at install time something like cygwin does
That's the approach I want to take with almost all extensions -- provide
add-ons through RubyGems.
Curt
···
il Thu, 22 Jul 2004 22:25:10 +0900, Laurent Sansonetti > <laurent.sansonetti@gmail.com> ha scritto::
il Thu, 22 Jul 2004 22:25:10 +0900, Laurent Sansonetti > <laurent.sansonetti@gmail.com> ha scritto::
>Hi Curt,
>
>Thanks for the package. I guess it's very convenient for Microsoft users.
>
>Just a question... do you plan to provide Ruby/GTK2 some day? GTK2
>works great on Windows and I believe it would be interesting to ship
>Ruby bindings for it, since you already deliver FOX bindings.
>
>(so there is no jalous
>
on the lines of the hread, I think the best thing would be to package
up all the ruby-gnome2 stuff that works on windows in some gems, and
maybe provide a choice at install time something like cygwin does
Mmh good idea. I will have a look at it after the next release. I
wonder how rubygems deal with dependencies.
I must have missed this one. But unfortunately I don't have an ME box to try it on anyway. If you could send me a detailed description, I can try to fix it "in theory" and you can be my testing department
Cheers
Dave
···
On Jul 23, 2004, at 7:46, Curt Hibbs wrote:
Does it fix ri bug related to PAGER in WinMe [ruby-talk:103662]?
The exact error message text is at work, sorry. I will dig it up next week if
you can't reproduce the problem I was seeing. It didn't look like a local
issue to me.
···
On Sat, Jul 24, 2004 at 10:48:15AM +0900, Curt Hibbs wrote:
Javier Fontan wrote:
>
> Hello,
>
> Will the final version have the opengl bindings? I was so surprised
> when I installed latest RC and opengl didn't come. Does opengl
> bindings have any problem?
>
> Bye, and thank you for the work.
Hmmm.... I think it should have been there. I'll have to look into what
happened. Thanks for the report.
--
Jos Backus _/ _/_/_/ Sunnyvale, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/ _/
jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer'
Ok, ok... I know I said no more releases until
1.8.2 final, but Matz just released 1.8.2
preview2 so I thought I would get an installer
out that includes this before I go on my vacation
tomorrow. There were no other changes since rc6 Enjoy!
Those are RDoc pages from a now old copy of 1.9. I believe I put them there because of issues at the time with folks getting RDoc/ri for 1.8.something
Ye, I realize the ruby-doc.org homepage has that link under "core API"; that needs to change, though I could not right this moment tell you when I will get to that.
Or something. Suggestions welcome. (I tend to prefer URLs that follow some sort of convention, such that if you see one or two you can make reasonable guesses about others, though things don't always evolve that way.)
At Sat, 31 Jul 2004 04:52:49 +0900,
Curt Hibbs wrote in [ruby-talk:107933]:
Ok, ok... I know I said no more releases until
1.8.2 final, but Matz just released 1.8.2
preview2 so I thought I would get an installer
out that includes this before I go on my vacation
tomorrow. There were no other changes since rc6 Enjoy!
Aren't you going to change the points which I wrote in
[ruby-talk:105550] and [ruby-talk:106176]?
* envrionment variables TCL_LIBRARY and RUBY_{TCL,TK}_DLL are
set.
Sure it would, if the package authors provide both source and
precompiled, "binary" gems for their packages. I don't know what
specific issues come into play with the ruby-postgres package, but
I've been experimenting with this in the alpha releases of FXRuby 1.2
and it seems to be working well.
> The way I want to address this problem is to include RubyGems in the
> installer, and then encourage package authors to release their packages in
> RubyGems format. Then getting ruby-postgres installed on your system would
> be as simple as running the command "gem install ruby-postgres".
But this does still not help on binary extensions.
> A public debate over what should or should not be included
has occurred
> several times in the past. As you might expect everyone has their own
> favorites. I'm sure that a very good case could be made for
each possible
> inclusion, but it is simply not practical to include too many
things, and
> its not possible satisfy everyone.
> The way I want to address this problem is to include RubyGems in the
> installer, and then encourage package authors to release
their packages in
> RubyGems format. Then getting ruby-postgres installed on your
system would
> be as simple as running the command "gem install ruby-postgres".
But this does still not help on binary extensions. And until the
brain dead (assuming the build system for extensions is the same as
the one for the original interpreter) and completely undocumented binary
build system "rb_configure.rb" etc. is changed this is a very
serious issue.
My personal request here is to include "wxruby.0.4"
RubyGems *does* support platform-specific binary gems. This was an issue
that I brought up early on with the RubyGems developers precisely because I
wanted to package up wxRuby as a set of platform-specific binary gems
(although that hasn't happened yet). Do you think that wxRuby is mature
enough?
Curt
PS
I still need to resolve your problem with TCL/TK extension. I sent you a
private email to your [mailinglists at scriptolutions dot com] address about
this, but perhaps it got spam-filtered into oblivion. After the postings
from you and [nobu.nokada at softhome dot net], it was not obvious to me
what the correct solution should be. If you could send me your email address
(send to curt at hibbs dot com), I will re-send you that email.
Thanks, -curt
> Javier Fontan wrote:
> >
> > Hello,
> >
> > Will the final version have the opengl bindings? I was so surprised
> > when I installed latest RC and opengl didn't come. Does opengl
> > bindings have any problem?
> >
> > Bye, and thank you for the work.
>
> Hmmm.... I think it should have been there. I'll have to look into what
> happened. Thanks for the report.
I commented out the OpenGL bindings because they were causing the
builder.rb
script to fail. This is reflected in the commit message, see
The exact error message text is at work, sorry. I will dig it up
next week if
you can't reproduce the problem I was seeing. It didn't look like a local
issue to me.
No, that's not the problem. Lyle Johnson sent me a new binary build which I
thought I included, but I must have screwed up somewhere. Anyway, I'll make
sure its back in for RC6 (which will probably be when matz releases 1.8.2
final).
Curt
···
On Sat, Jul 24, 2004 at 10:48:15AM +0900, Curt Hibbs wrote:
Here's what I do to track down the problem.
I use the latest ruby182-14_rc5.exe from Ruby Installer on rubyforge.
First I add some debug info to ri_display.rb
···
On Fri, Jul 23, 2004 at 09:59:57PM +0900, Dave Thomas wrote:
On Jul 23, 2004, at 7:46, Curt Hibbs wrote:
>>Does it fix ri bug related to PAGER in WinMe [ruby-talk:103662]?
I must have missed this one. But unfortunately I don't have an ME box
to try it on anyway. If you could send me a detailed description, I can
try to fix it "in theory" and you can be my testing department
=============================================================================
--- ri_display.rb.orig 2004-03-25 22:31:10.000000000 +0700
+++ ri_display.rb 2004-07-26 16:35:30.000000000 +0700
@@ -223,11 +223,16 @@ @save_stdout = nil
paged = false
for pager in [ ENV['PAGER'], "less", "more <", 'pager' ].compact.uniq
+STDERR.puts "#{pager} #{path}"
if system("#{pager} #{path}")
paged = true
break
end
end
+STDERR.puts "paged: #{paged}"
+STDERR.print 'Press Enter'
+STDERR.flush
+STDIN.readline
if !paged @options.use_stdout = true
puts File.read(path)
The I try to run ri in DOS Prompt
C:\WINDOWS\Desktop>ri String
less C:/WINDOWS/TEMP/ri_256695.0
more < C:/WINDOWS/TEMP/ri_256695.0
File not found
paged: true
Press Enter
The problem is in system("more < file"). I try similar thing with irb
irb(main):001:0> system "more < c:\autoexec.bat"
File not found
=> true
Same result.
I did more experiment on irb
irb(main):002:0> system 'more c:\autoexec.bat'
=> false
irb(main):003:0> system 'more.com c:\autoexec.bat'
SET windir=C:\WINDOWS
SET winbootdir=C:\WINDOWS
SET COMSPEC=C:\WINDOWS\COMMAND.COM
SET PROMPT=$p$g
SET TEMP=C:\WINDOWS\TEMP
SET TMP=C:\WINDOWS\TEMP
SET TCL_LIBRARY=c:\ruby\tcl\lib\tcl8.3
SET RUBY_TCL_DLL=c:\ruby\bin\tcl83.dll
SET RUBY_TK_DLL=c:\ruby\bin\tk83.dll
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;c:\ruby\bin
=> true
irb(main):004:0> system 'more.com < c:\autoexec.bat'
SET windir=C:\WINDOWS
SET winbootdir=C:\WINDOWS
SET COMSPEC=C:\WINDOWS\COMMAND.COM
SET PROMPT=$p$g
SET TEMP=C:\WINDOWS\TEMP
SET TMP=C:\WINDOWS\TEMP
SET TCL_LIBRARY=c:\ruby\tcl\lib\tcl8.3
SET RUBY_TCL_DLL=c:\ruby\bin\tcl83.dll
SET RUBY_TK_DLL=c:\ruby\bin\tk83.dll
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;c:\ruby\bin
=> true
It appear I must use 'more.com'. So I add 'more.com' before 'more <'
for pager in [ ENV['PAGER'], "less", "more.com", "more <", 'pager' ].compact.uniq
Here's the result
C:\WINDOWS\Desktop>ri String
less C:/WINDOWS/TEMP/ri_256695.0
more.com C:/WINDOWS/TEMP/ri_256695.0
Invalid switch
paged: true
Press Enter
I believe that because the path is in UNIX style, so 'more' think it is a
DOS style command-line switch (/something).
The question is:
1. Why system('more') doesn't find more.com?
2. Why the path is in UNIX style?
3. How to change it to DOS style?
I'm in a rush at the moment, but I wanted say, just let me know what URL you
want me to use. Also, If you want me to add anything else, let me know that,
too.
Thanks,
Curt
···
-----Original Message-----
From: James Britt [mailto:jamesUNDERBARb@neurogami.com]
Sent: Friday, July 30, 2004 3:53 PM
To: ruby-talk ML
Cc: rubyinstaller-announce@rubyforge.org
Subject: Re: [ANN] Ruby Installer for Windows 1.8.2-14 **RC7**
Curt Hibbs wrote:
> Ok, ok... I know I said no more releases until
> 1.8.2 final, but Matz just released 1.8.2
> preview2 so I thought I would get an installer
> out that includes this before I go on my vacation
> tomorrow. There were no other changes since rc6 Enjoy!
>
> Curt
>
> You can download this release candidate from:
> http://rubyforge.org/frs/?group_id=167
>
>
> ===== Original Text from RC6 Release =====
>
...
> - Start menu shortcuts have been
> added to online documentation on
> ruby-doc.org.
The shortcut to the stdlib should be fine; the shortcut to core libs is
not.
Those are RDoc pages from a now old copy of 1.9. I believe I put them
there because of issues at the time with folks getting RDoc/ri for
1.8.something
Ye, I realize the ruby-doc.org homepage has that link under "core API";
that needs to change, though I could not right this moment tell you when
I will get to that.
Or something. Suggestions welcome. (I tend to prefer URLs that follow
some sort of convention, such that if you see one or two you can make
reasonable guesses about others, though things don't always evolve that
way.)
James
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.726 / Virus Database: 481 - Release Date: 7/22/2004
At Sat, 31 Jul 2004 04:52:49 +0900,
Curt Hibbs wrote in [ruby-talk:107933]:
> Ok, ok... I know I said no more releases until
> 1.8.2 final, but Matz just released 1.8.2
> preview2 so I thought I would get an installer
> out that includes this before I go on my vacation
> tomorrow. There were no other changes since rc6 Enjoy!
Aren't you going to change the points which I wrote in
[ruby-talk:105550] and [ruby-talk:106176]?
* environment variables TCL_LIBRARY and RUBY_{TCL,TK}_DLL are
set.
* duplicated files.
--
Nobu Nakada
I wanted to make these changes, but when I started to make the changes, it
wasn't clear precisely what I was supposed to do. At that time I sent you a
private email (to nobu.nokada@softhome.net) listing what I thought should be
done and asking if that was correct, but I never got a response before I had
to leave for my vacation.
Below is what I sent you (please let me know if this is correct).
Thank you,
Curt
···
nobu.nokada@softhome.net wrote:
-----Original Message-----
From: Curt Hibbs [mailto:curt@curthibbs.us]
Sent: Friday, July 16, 2004 12:47 PM
To: nobu.nokada@softhome.net
Cc: Curt Hibbs
Subject: Corrections for TCL/TK
nobu.nokada@softhome.net wrote:
At Thu, 8 Jul 2004 20:06:36 +0900,
Curt Hibbs wrote in [ruby-talk:105566]:
> > No, eban says those environment variables are not need at all.
> > RubyInstaller should just set PATH, but not TCL_LIBRARY. And
> > RUBY_{TCL,TK}_DLL are used only if tcltklib is compiled with
> > --enable-tcltk_stubs, but RubyInstaller doesn't.
>
> Good, I like that even better! I will change the installer to not set
> TCL_LIBRARY.
Correction: It couldn't find tk.tcl file when it just is not
set. It worked by moving tcl/lib/* to lib.
Another issue, there are identical files under samples/sample
and doc/Tcl/Tk-1.8.1/sample, except for several files only in
the former. Instead, *.{rb,so,lib} underneath lib are
superfluous, since they exist also under lib/ruby/1.8 and never
be used.
I am making changes to the ruby installer build in preparation for matz'
1.8.2 preview1, and I want to make sure that I correctly understand what you
have said needs to be done to fix TCL/TK in the ruby installer. This is
particularly important since I do not know anything about TCL/TK myself and
I rely on others for this advice and eventual testing.
I think the easiest way to do this is to assume that my last release
candidate, ruby182-14_rc3.exe, has been installed in the default location
(c:\ruby), and I will then describe the changes I think need to be made
using absolute paths. I'm fairly certain that this is wrong, but this is
what I got determined from your emails:
... if you promise not to laugh at the code, I'll privately send
you what I've got and you can tell me what to do to get it up to the
specs you'd want/need for inclusion in the Windows Installer.
The way I envision it is that the RubyGem interface would be a
compiled binary for Windows, that could have a link in the Programs
menu... then for the average 10yr old, or mom or dad who wanted to
program, they could easily add libraries on to their Ruby
installation... Double-click the RubyGem interface... wait for the
list to load... select the program, see all versions and a
description, select the version to install... click the install
button... you're done. Obviously there would be more options for
advanced users... but I really like the idea of making the
installation of add-on libraries as simple as the installation of
Ruby.
I really want RubyGems in the Windows One-Click... and I _really_
think RubyGems should have a GUI... i.e. I really want to send you my
code, have it reviewed, get everything done that you need, and package
it with the Windows One-Click.
-Rich
P.s. - Windows One-Click.... WOC? Sounds like Wok... which I know
is Chinese, and not Japanese... but it's an interesting acronym. Would
that make it... LOC (Linux...), MOC, (Mac...) ... anyway...
Lothar Scholz wrote:
>
> Hello Curt,
>
> > A public debate over what should or should not be included
> has occurred
> > several times in the past. As you might expect everyone has their own
> > favorites. I'm sure that a very good case could be made for
> each possible
> > inclusion, but it is simply not practical to include too many
> things, and
> > its not possible satisfy everyone.
>
> > The way I want to address this problem is to include RubyGems in the
> > installer, and then encourage package authors to release
> their packages in
> > RubyGems format. Then getting ruby-postgres installed on your
> system would
> > be as simple as running the command "gem install ruby-postgres".
>
> But this does still not help on binary extensions. And until the
> brain dead (assuming the build system for extensions is the same as
> the one for the original interpreter) and completely undocumented binary
> build system "rb_configure.rb" etc. is changed this is a very
> serious issue.
>
> My personal request here is to include "wxruby.0.4"
RubyGems *does* support platform-specific binary gems. This was an issue
that I brought up early on with the RubyGems developers precisely because I
wanted to package up wxRuby as a set of platform-specific binary gems
(although that hasn't happened yet). Do you think that wxRuby is mature
enough?
Curt
PS
I still need to resolve your problem with TCL/TK extension. I sent you a
private email to your [mailinglists at scriptolutions dot com] address about
this, but perhaps it got spam-filtered into oblivion. After the postings
from you and [nobu.nokada at softhome dot net], it was not obvious to me
what the correct solution should be. If you could send me your email address
(send to curt at hibbs dot com), I will re-send you that email.
Thanks, -curt
And, we are adding to Gems the ability to utilize the platform attribute
within the gemspec to select the appropriate binary vs. source gem (or give
the user the option) if provided. So if Lyle puts:
It will pick (not based on the name, that is convention) the fxruby 1.2.0
for your platform if one exists.
If a Linux user did:
gem install -r fxruby
RubyGems would download fxruby-1.2.0.gem and it would build it (using the
extconf.rb, etc) upon install from source.
If a Windows user did:
gem install -r fxruby
RubyGems would download fxruby-1.2.0-win32.gem and it would just install (no
building necessary).
This automatic selection capability will be in Gems SOON (hopefully in a
week), but as Lyle said, you can currently build and install gems that are
binary but its a manual choosing process.
-rich
···
On 7/22/04 9:05 AM, "Lyle Johnson" <lyle.johnson@gmail.com> wrote:
> The way I want to address this problem is to include RubyGems in the
> installer, and then encourage package authors to release their packages
in
> RubyGems format. Then getting ruby-postgres installed on your system
would
> be as simple as running the command "gem install ruby-postgres".
But this does still not help on binary extensions.
Sure it would, if the package authors provide both source and
precompiled, "binary" gems for their packages. I don't know what
specific issues come into play with the ruby-postgres package, but
I've been experimenting with this in the alpha releases of FXRuby 1.2
and it seems to be working well.
"Curt Hibbs" <curt@hibbs.com> wrote in message news:<EAENKKNOJPMNCDMLDOMLOEAPFDAA.curt@hibbs.com>...
Lothar Scholz wrote:
[...]
> But this does still not help on binary extensions. And until the
> brain dead (assuming the build system for extensions is the same as
> the one for the original interpreter) and completely undocumented binary
> build system "rb_configure.rb" etc. is changed this is a very
> serious issue.
>
> My personal request here is to include "wxruby.0.4"
RubyGems *does* support platform-specific binary gems. This was an issue
that I brought up early on with the RubyGems developers precisely because I
wanted to package up wxRuby as a set of platform-specific binary gems
(although that hasn't happened yet). Do you think that wxRuby is mature
enough?
RubyGems supports binary gems in the sense that you can put any file
type, including binary, into a gem. But there is no useful support
for binary gems; I asked in [ruby-talk:104609] and [ruby-talk:104486]
and in private email, all without reply. (By "binary" I mean
precompiled gems.)
For my gems, I experimented with a mypackage-i686-linux-ruby18-1.2.3.gem
naming scheme but decided it was too polluting to the global gem list
since every platform must have a separate, "unrelated" gem. The naming
scheme mypackage-1.2.3-i686-linux-ruby18.gem is a "Malformed version
number" error. The precompiled gems were also about twice as large as
a .tbz2 of the same files.
I eventually decided to stick with tarballs with .so files until
rubygems formally supports precompiled extensions.
This could be implemented by recognizing a -linux-i686-ruby18 suffix,
for example. Currently, when mypackage-1.2.3-i686-linux-ruby18.gem
exists on gems.rubyforge.org/gems/, there is a 404 Not Found error
for "gem -i mypackage". A first step could be to find gems matching
the host platform suffix when the primary search fails or when the
user requests a binary gem.
> > Hmmm.... I think it [opengl] should have been there. I'll have to look
into what
> > happened. Thanks for the report.
Yeah, I messed this one up... I just figure out what I did. Opengl support
will be in the next release candidate (which will probably be when matz
releases the final 1.8.2).
If anyone needs the opengl support right away, let me know and I will email
the binary files to you.
Okay, glad to hear that's working again, Curt. It wasn't at the time I checked
in the change.
Thanks,
···
On Sat, Jul 24, 2004 at 01:56:11PM +0900, Curt Hibbs wrote:
Jos Backus wrote:
>
> On Sat, Jul 24, 2004 at 10:48:15AM +0900, Curt Hibbs wrote:
> > Javier Fontan wrote:
> > >
> > > Hello,
> > >
> > > Will the final version have the opengl bindings? I was so surprised
> > > when I installed latest RC and opengl didn't come. Does opengl
> > > bindings have any problem?
> > >
> > > Bye, and thank you for the work.
> >
> > Hmmm.... I think it should have been there. I'll have to look into what
> > happened. Thanks for the report.
>
> I commented out the OpenGL bindings because they were causing the
> builder.rb
> script to fail. This is reflected in the commit message, see
>
> http://rubyforge.org/cgi-bin/viewcvs/cgi/viewcvs.cgi/installer/bui
> lder/builder.rb?rev=1.8&cvsroot=rubyinstaller&content-type=text/vn
> d.viewcvs-markup
>
> The exact error message text is at work, sorry. I will dig it up
> next week if
> you can't reproduce the problem I was seeing. It didn't look like a local
> issue to me.
No, that's not the problem. Lyle Johnson sent me a new binary build which I
thought I included, but I must have screwed up somewhere. Anyway, I'll make
sure its back in for RC6 (which will probably be when matz releases 1.8.2
final).
--
Jos Backus _/ _/_/_/ Sunnyvale, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/ _/
jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer'
