so i went ahead and started moving over to 1.7.
but a ways into it i realized i had no idea how to properly do so.
i started by compiling 1.7.3 from source and that went fine. and works.
but all my libraries are in /usr/local/lib/site-ruby/1.6. ruby 1.7 has a
slightly different dir structure: /usr/local/lib/ruby/site-ruby/1.7. so
i just thought all i would need to do is copy all the stuff in 1.6 to
this 1.7 directory. so i did.
but now DBD/DBI doesn’t work, saying it can’t find the Pg driver. that’s
when i realized i’m not at all sure how i should be going about this.
what’s the proper way to upgrade to 1.7+?
FYI- i run debian woody and had 1.6.5 via apt-get, and i haven’t yet
uninstalled it.
-transami
i did just figure one part of this: i have to apt-get uninstall every
ruby library i have installed via apt-get, and reinstall them all from
source. ouch.
but that’ll probably fix my postgresql problem. (?)
hmmm…i wish rpkg had more packages! don’t you all think its about time
to convert the RAA over to utilizing rpkg? i think rpkg really needs to
become a standard part of ruby. us debian folk know why 
and, one more thing. i don’t think these version directories under
site-ruby are a good idea. why have them? most packages will work just
fine from one update to another. and if one does not, shouldn’t the
package maintainer take care of the versioning within the package
itself? just some thoughts that may make life a easier.
~transami
···
On Fri, 2002-08-30 at 17:53, Tom Sawyer wrote:
so i went ahead and started moving over to 1.7.
but a ways into it i realized i had no idea how to properly do so.
i started by compiling 1.7.3 from source and that went fine. and works.
but all my libraries are in /usr/local/lib/site-ruby/1.6. ruby 1.7 has a
slightly different dir structure: /usr/local/lib/ruby/site-ruby/1.7. so
i just thought all i would need to do is copy all the stuff in 1.6 to
this 1.7 directory. so i did.
but now DBD/DBI doesn’t work, saying it can’t find the Pg driver. that’s
when i realized i’m not at all sure how i should be going about this.
what’s the proper way to upgrade to 1.7+?
FYI- i run debian woody and had 1.6.5 via apt-get, and i haven’t yet
uninstalled it.
-transami
–
~transami
on second thought that won’t solve my problem. most souce install
scripts install to 1.6 anyway.
hmm… maybe i should just move everything back and add the 1.6 path to
1.7’s $LOAD_PATH. or something like that.
~transami
···
On Fri, 2002-08-30 at 18:41, Tom Sawyer wrote:
i did just figure one part of this: i have to apt-get uninstall every
ruby library i have installed via apt-get, and reinstall them all from
source. ouch.
but that’ll probably fix my postgresql problem. (?)
hmmm…i wish rpkg had more packages! don’t you all think its about time
to convert the RAA over to utilizing rpkg? i think rpkg really needs to
become a standard part of ruby. us debian folk know why
and, one more thing. i don’t think these version directories under
site-ruby are a good idea. why have them? most packages will work just
fine from one update to another. and if one does not, shouldn’t the
package maintainer take care of the versioning within the package
itself? just some thoughts that may make life a easier.
~transami
On Fri, 2002-08-30 at 17:53, Tom Sawyer wrote:
so i went ahead and started moving over to 1.7.
but a ways into it i realized i had no idea how to properly do so.
i started by compiling 1.7.3 from source and that went fine. and works.
but all my libraries are in /usr/local/lib/site-ruby/1.6. ruby 1.7 has a
slightly different dir structure: /usr/local/lib/ruby/site-ruby/1.7. so
i just thought all i would need to do is copy all the stuff in 1.6 to
this 1.7 directory. so i did.
but now DBD/DBI doesn’t work, saying it can’t find the Pg driver. that’s
when i realized i’m not at all sure how i should be going about this.
what’s the proper way to upgrade to 1.7+?
FYI- i run debian woody and had 1.6.5 via apt-get, and i haven’t yet
uninstalled it.
-transami
–
~transami
–
~transami
“Tom Sawyer” transami@transami.net wrote in message
news:1030755047.543.36.camel@silver…
and, one more thing. i don’t think these version directories under
site-ruby are a good idea. why have them? most packages will work just
fine from one update to another. and if one does not, shouldn’t the
package maintainer take care of the versioning within the package
itself? just some thoughts that may make life a easier.
Extension modules built for Ruby 1.6 are almost guaranteed not to work for
Ruby 1.7.
I have found that most modules are straigtforward to build.
Typically download the source and:
ruby extconf.rb
make
make install
Even on windows:
ruby extconf.rb
nmake
nmake install
Assuming you have libraries needed for extension.
-rich
···
-----Original Message-----
From: Lyle Johnson [mailto:lyle@knology.net]
Sent: Friday, August 30, 2002 9:56 PM
To: ruby-talk ML
Subject: Re: proper upgrade to 1.7.3
“Tom Sawyer” transami@transami.net wrote in message
news:1030755047.543.36.camel@silver…
and, one more thing. i don’t think these version directories under
site-ruby are a good idea. why have them? most packages
will work just
fine from one update to another. and if one does not, shouldn’t the
package maintainer take care of the versioning within the package
itself? just some thoughts that may make life a easier.
Extension modules built for Ruby 1.6 are almost guaranteed
not to work for Ruby 1.7.
duh! i totally spaced the fact that the compiled libraries would have to
be recompiled for 1.7+ and would thus be installed to the correct
location. silly me! 
the pure ruby packages would probably be just fine though, but i might
as well reinstall them too while i’m at it.
-transami
···
On Fri, 2002-08-30 at 21:00, Rich Kilmer wrote:
I have found that most modules are straigtforward to build.
Typically download the source and:
ruby extconf.rb
make
make install
Even on windows:
ruby extconf.rb
nmake
nmake install
Assuming you have libraries needed for extension.
-rich
-----Original Message-----
From: Lyle Johnson [mailto:lyle@knology.net]
Sent: Friday, August 30, 2002 9:56 PM
To: ruby-talk ML
Subject: Re: proper upgrade to 1.7.3
“Tom Sawyer” transami@transami.net wrote in message
news:1030755047.543.36.camel@silver…
and, one more thing. i don’t think these version directories under
site-ruby are a good idea. why have them? most packages
will work just
fine from one update to another. and if one does not, shouldn’t the
package maintainer take care of the versioning within the package
itself? just some thoughts that may make life a easier.
Extension modules built for Ruby 1.6 are almost guaranteed
not to work for Ruby 1.7.
–
~transami