From: Phillip Gawlowski <cmdjackryan@...>
Date: 2008-04-07T23:30:24+09:00
Subject: Re: gem build documentation for new gems?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerardo Santana G�mez Garrido wrote:

| Well, Luis Lavena's work is promising. It's time for extension
| developers to try this environment and make the changes needed. After
| that, anybody would be able to automatically download and build
| extensions.

It indeed is. However, the best solution would be to offer an SDKish
package for developers, and a RREish (Ruby Runtime Environment :P) at
the same time. The former for developers, and the latter for end-users.

However, this distinction is a bit blurry, with Ruby not compiling to
byte-code/machine code, and not needing a compiler environment as Java does.

However, I'm of the opinion that nobody who doesn't want to, shouldn't
*have to* compile extensions.

And to handle these case, it is necessary to define a way to handle
header files and source files on the one hand, and to handle "just" the
extensions in a neat way (integrated to RubyGems would be best.
Something like a #has_gcc_compiler? method.

*shrugs*

- --
Phillip Gawlowski
Twitter: twitter.com/cynicalryan

At the source of every error which is blamed on the computer you will
find at
least two human errors, including the error of blaming it on the computer.
~ -- Tom Gibb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf6L/8ACgkQbtAgaoJTgL88PQCfSqTE8HuN5Ir1Rf0j24O2YDGn
ypEAoKTSf1BWphH3mAMj51UbiEqE2ER2
=YUgW
-----END PGP SIGNATURE-----