From: Tilman Sauerbeck <tilman@...>
Date: 2006-08-13T05:40:58+09:00
Subject: Re: Rubygem libs vs Non Rubygem libs

--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

darren kirby [2006-08-13 05:34]:
> quoth the lists:
> > Try this:
> >
> > ruby -e "require 'rubygems'; require 'xml-simple'"
> >
> > You have to require rubygems first.
>=20
> Sorry to hijack here, but this is an issue that has sort of unsettled me =
as I=20
> have seen it come up on this list a few times. Perhaps I am not understan=
ding=20
> gems fully here, but what if you are writing software to be released to t=
he=20
> public that relies on a 3rd party library?
>=20
> Some might have the lib installed from gems and some might have installed=
=20
> manually or whatever ... so how do you reconcile the two if you must requ=
ire=20
> rubygems to use gem installed libs? Why is the gems directory not added t=
o=20
> the regular include path? Are you required to write code to deal with thi=
s?=20
> How do experienced Ruby devs deal with this issue? Or am I just thick and=
 it=20
> isn't an issue at all?
>=20
> any insight appreciated,

export RUBYOPT=3Drubygems

The you can use "require" to load both gem-libraries and
non-gem-libraries.

Regards,
Tilman

--=20
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE3jzW27uLisrW2w8RAmqDAJ9ejKrk0EM9jrsYqUPwBmFnT/AAOQCfWGMc
2Rz9QIVwsZ1skPLXXdIYm7A=
=Wfni
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--