I'm using the iconv library form the Ruby Standard Library under Linux
and it works quite well, but the iconv library is not available under
Windows (using the One-Click-Installer). Is there anything equivalent to
iconv in Ruby for Windows?
My recommendation is to request that iconv be included with the
One-Click-Installer.
-austin
···
On Sat, 11 Dec 2004 00:17:30 +0900, Thomas Leitner <t_leitner@gmx.at> wrote:
I'm using the iconv library form the Ruby Standard Library under Linux
and it works quite well, but the iconv library is not available under
Windows (using the One-Click-Installer). Is there anything equivalent to
iconv in Ruby for Windows?
I have looked at the feature request page of the One-Click-Installer
project and there is already a feature request for iconv. Thanks for
pointing me to that!
Thomas
···
On Sat, 11 Dec 2004 00:45:11 +0900 Austin Ziegler <halostatue@gmail.com> wrote:
On Sat, 11 Dec 2004 00:17:30 +0900, Thomas Leitner <t_leitner@gmx.at> > wrote:
> I'm using the iconv library form the Ruby Standard Library under
> Linux and it works quite well, but the iconv library is not
> available under Windows (using the One-Click-Installer). Is there
> anything equivalent to iconv in Ruby for Windows?
My recommendation is to request that iconv be included with the
One-Click-Installer.
--
\ Thomas Leitner -- thomas [underscore] leitner [at] gmx [dot] at
/ "Life is what happens to you while you're busy making other plans"
> > I'm using the iconv library form the Ruby Standard Library under
> > Linux and it works quite well, but the iconv library is not
> > available under Windows (using the One-Click-Installer). Is there
> > anything equivalent to iconv in Ruby for Windows?
>
> My recommendation is to request that iconv be included with the
> One-Click-Installer.
>
I have looked at the feature request page of the One-Click-Installer
project and there is already a feature request for iconv. Thanks for
pointing me to that!
If someone would be willing to package iconv as a RubyGem, them it would
become immediately available thru a simple "gem install iconv", since
RubyGems is now included in the one-click installer.
Curt
···
On Sat, 11 Dec 2004 00:45:11 +0900 > Austin Ziegler <halostatue@gmail.com> wrote:
> On Sat, 11 Dec 2004 00:17:30 +0900, Thomas Leitner <t_leitner@gmx.at> > > wrote:
If someone would be willing to package iconv as a RubyGem, them it would
become immediately available thru a simple "gem install iconv", since
RubyGems is now included in the one-click installer.
Curt
yes, but iconv is one of the things that is part of the standard ruby (it is a c bingind in /ext) so it would be nice to see it provided with the standard 1-click-installer (maybe with the proper iconv utility)
Right. If it's provided with standard Ruby (e.g., OpenSSL, iconv, a
few other things), then the 1-click installer should include them.
I personally don't like the idea of forcing users to use RubyGems for
a lot of things that are currently in the installer.
-austin
···
On Sat, 11 Dec 2004 04:57:24 +0900, gabriele renzi <rff_rff@remove-yahoo.it> wrote:
Curt Hibbs ha scritto:
> If someone would be willing to package iconv as a RubyGem, them it would
> become immediately available thru a simple "gem install iconv", since
> RubyGems is now included in the one-click installer.
yes, but iconv is one of the things that is part of the standard ruby
(it is a c bingind in /ext) so it would be nice to see it provided with
the standard 1-click-installer (maybe with the proper iconv utility)
>
> If someone would be willing to package iconv as a RubyGem, them it would
> become immediately available thru a simple "gem install iconv", since
> RubyGems is now included in the one-click installer.
>
> Curt
yes, but iconv is one of the things that is part of the standard ruby
(it is a c bingind in /ext) so it would be nice to see it provided with
the standard 1-click-installer (maybe with the proper iconv utility)
<embarrassed> That'll teach me to dash off a quick reply before heading out
to a meeting!
My intention was to use this as an encouragement to use RubyGems, but I sure
did pick the wrong thing!
i have iconv with my win32 GTK install (gaim),
i have iconv with my apache2 install
i have iconv with my php install
i have iconv with cygwin
i have iconv with DevCPP
i have iconv with subversion
i also have some inconv dlls in my windows\system32 which I dont
know what app owns.
i dont mind having the world + kitchen sink in the 1click installer
as long as I can checkbox it out and not break anything if I have
iconv installed by something else already.
where is the line? if we add openssl are we going to add mysql just
for kicks? or postgresql? how about a c compiler since some extensions
require compilation??
On Sat, 11 Dec 2004 05:22:38 +0900, Austin Ziegler <halostatue@gmail.com> wrote:
On Sat, 11 Dec 2004 04:57:24 +0900, gabriele renzi ><rff_rff@remove-yahoo.it> wrote:
Curt Hibbs ha scritto:
> If someone would be willing to package iconv as a RubyGem, them it would
> become immediately available thru a simple "gem install iconv", since
> RubyGems is now included in the one-click installer.
yes, but iconv is one of the things that is part of the standard ruby
(it is a c bingind in /ext) so it would be nice to see it provided with
the standard 1-click-installer (maybe with the proper iconv utility)
Right. If it's provided with standard Ruby (e.g., OpenSSL, iconv, a
few other things), then the 1-click installer should include them.
I personally don't like the idea of forcing users to use RubyGems for
a lot of things that are currently in the installer.
For extra/external libraries, I can agree with you. Thus, iconv.dll
should only be installed when it is selected (which it should be, by
default). However, iconv.so -- the Ruby interface to iconv -- must
be installed regardless. Maybe the installer can check to see if it
can load iconv.dll from the PATH before it selects the iconv.dll
installation by default.
MySQL and PostgresQL (the databases, not the bindings) would not be
included because they are clearly separate libraries that a user
must want to use. Iconv and OpenSSL are *assumed* by Ruby to be part
of a working operating system.
At a minimum, the Ruby bindings must be included. If there are
redistributables (e.g., openssl.dll, iconv.dll) that would be
beneficial, they should be included but made optional for
installation.
The point is to have a complete installer for people who would run
our applications, not just programmers. If not, then we tell people
on Windows to download and install fifteen things *before they can
even RUN Ruby*.
-austin
···
On Sun, 12 Dec 2004 05:12:34 +0900, Stu <ceaser@rome.net> wrote:
On Sat, 11 Dec 2004 05:22:38 +0900, Austin Ziegler > <halostatue@gmail.com> wrote:
On Sat, 11 Dec 2004 04:57:24 +0900, gabriele renzi >> <rff_rff@remove-yahoo.it> wrote:
Curt Hibbs ha scritto:
If someone would be willing to package iconv as a RubyGem, them
it would become immediately available thru a simple "gem
install iconv", since RubyGems is now included in the one-click
installer.
yes, but iconv is one of the things that is part of the standard
ruby (it is a c bingind in /ext) so it would be nice to see it
provided with the standard 1-click-installer (maybe with the
proper iconv utility)
Right. If it's provided with standard Ruby (e.g., OpenSSL, iconv,
a few other things), then the 1-click installer should include
them.
I personally don't like the idea of forcing users to use RubyGems
for a lot of things that are currently in the installer.
i have iconv with my win32 GTK install (gaim),
i have iconv with my apache2 install
i have iconv with my php install
i have iconv with cygwin
i have iconv with DevCPP
i have iconv with subversion
i also have some inconv dlls in my windows\system32 which I dont
know what app owns.
Hopefully you'll be able to configure all of these to use ruby's iconv and
stop the duplication.
i dont mind having the world + kitchen sink in the 1click installer
as long as I can checkbox it out and not break anything if I have
iconv installed by something else already.
That's a good idea.
where is the line? if we add openssl are we going to add mysql just
for kicks? or postgresql? how about a c compiler since some extensions
require compilation??
The extensions in ruby's ext directory. And they should come precompiled.
i have iconv with my win32 GTK install (gaim),
i have iconv with my apache2 install
i have iconv with my php install
i have iconv with cygwin
i have iconv with DevCPP
i have iconv with subversion
i also have some inconv dlls in my windows\system32 which I dont
know what app owns.
i dont mind having the world + kitchen sink in the 1click installer
as long as I can checkbox it out and not break anything if I have
iconv installed by something else already.
where is the line? if we add openssl are we going to add mysql just
for kicks? or postgresql? how about a c compiler since some extensions
require compilation??
People tend to think that if it's installed with Ruby on other
systems, it should be installed on Windows with Ruby as well. That
includes openssl and iconv, and omits mysql, postgresql, and a C
compiler
Gavin
···
On Sunday, December 12, 2004, 7:12:34 AM, Stu wrote:
where is the line? if we add openssl are we going to add mysql just
for kicks? or postgresql? how about a c compiler since some extensions
require compilation??
like i said, I have nothing against loading the installer with
everything under the sun, its a great way to distribute a base
install etc.
and id love to see more binary extensions come with the installer,
for things that are a PITA to build oneself (ala mod_ruby, db drivers,
ncurses, etc).
its easy to say XYZ is in rubygems, and it would be quite easy
for a non-programmer to gem install XYZ.. but do we expect
non-programmers to have compilers installed if they try to
gem install ncurses??
the other side of the coin is a base ruby install with nothing else
and some secondary install packs, say ruby-database-1click-installer
or ruby-widgets-1click for gtk/wx/fox/etc, mm im going off on tangents
now...
On Sun, 12 Dec 2004 06:40:20 +0900, Austin Ziegler <halostatue@gmail.com> wrote:
At a minimum, the Ruby bindings must be included. If there are
redistributables (e.g., openssl.dll, iconv.dll) that would be
beneficial, they should be included but made optional for
installation.
The point is to have a complete installer for people who would run
our applications, not just programmers. If not, then we tell people
on Windows to download and install fifteen things *before they can
even RUN Ruby*.
On Dec 12, 2004, at 2:13 AM, Gavin Sinclair wrote:
On Sunday, December 12, 2004, 7:12:34 AM, Stu wrote:
where is the line? if we add openssl are we going to add mysql just
for kicks? or postgresql? how about a c compiler since some extensions
require compilation??
People tend to think that if it's installed with Ruby on other
systems, it should be installed on Windows with Ruby as well. That
includes openssl and iconv, and omits mysql, postgresql, and a C
compiler
yup works fine. there was at some point a perfectly working
ruby mswin32 build that worked well with the pdcurses download
though i can't find this anymore. domain was d4win or something
from what i recall. but its been a while.
unfortunately the one-click installer has never supported it so
i've had to steer away from it
Alex
···
On Dec 14, 2004, at 4:32 PM, gabriele renzi wrote:
Daniel Berger ha scritto:
Alexander Kellett wrote:
curses would sure be nice
Without cygwin, the closest I think you can get is win32-console.
Available on the RAA.
I may be wrong, but IIRC, ext/curses worked reasonably when compiled with pdcurses.