From: Luis Lavena <luislavena@...>
Date: 2010-11-10T09:20:16+09:00
Subject: Re: Using Ruby's C API safely and sanely

On Nov 9, 10:35 am, Eric MSP Veith <eve...@wwweb-library.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Luis,
>
> On Monday 08 November 2010, Luis Lavena <luislav...@gmail.com> wrote:
>
> > Ruby trunk includes a package configuration file.
>
> > You should checkout trunk and use it as base of your project.
>
> thanks for the hint. Do you by chance know in which releases the file will
> appear? E.g., is there a plan to backport it to the 1.8 series?
>

1.9.3

I believe it will not be backported to 1.8.x branch. Perhaps 1.9.2

> The problem basically is that RPM has to deal with whatever version is
> installed on the target system, and most distros still ship one of the 1.8
> releases. So it's nice to know that there will be a pkg-config file
> appearing in the distro's packages in the future, but we cannot base RPM's
> embedded ruby or the bindings code on ruby trunk.
>

Well, the other approach you have is build ruby statically and use it
embedded and not depend of installed package version.

Ruby in this way is way too bigger. build statically and link against
it sounds much safer for your scenario.

Other languages like Lua are easy to embed and simple to handle, but
if you're building your component depending on installed version, you
will suffer the same issues no matter what language are you trying to
embed.

--
Luis Lavena