From: Urabe Shyouhei <shyouhei@...>
Date: 2009-08-27T10:30:12+09:00
Subject: [ruby-core:25150] Re: [Bug #1991] ruby should use twolevel namespace on OS X

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF8887F9F24736E2AEC37A7C0
Content-Type: multipart/mixed;
 boundary="------------040504060602070908000807"

This is a multi-part message in MIME format.
--------------040504060602070908000807
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Michal Suchanek wrote:
>>> - change the library name from libruby to libruby1.8 to prevent clash=
es with libruby1.9 (or something like that)
>> Reject.  1.9 uses libruby.1.9.1.dylib already, no needs to
>> change 1.8.
>>
>=20
> It should not affect complete ruby installations but it helps packaged
> installations where multiple versions of the library coexist (such as
> 1.6 and 1.8). It allows installing the libruby link (and headers)
> pointing to one of the libraries and still use executables linked with
> both libraries.
>=20
> When 1.8 uses libruby (without version in name) as the soname it is
> impossible to install binaries linked with ruby 1.8 along with
> development files for another ruby version, be it 1.6 or 1.9.

Don't wake a sleeping dog.  1.6 has been abandoned for at least 6 years.




--------------040504060602070908000807
Content-Type: application/pgp-signature;
 name="signature.asc"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="signature.asc"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuNC45IChH
TlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly9l
bmlnbWFpbC5tb3pkZXYub3JnCgppRVlFQVJFQ0FBWUZBa3FWYWlnQUNna1F1VFhQVW5BNWVN
SkVQUUNmY3R3ejRiNTdoeUsxK05lNUNVL3NkTUF1CmhnMEFuMHh4a1lLNVZwR2d2NnVmaVMy
dUkzN2V1TFdUCj1MbDJ1Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQoK
--------------040504060602070908000807
Content-Type: application/pgp-signature;
 name="signature.asc"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="signature.asc"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuNC45IChH
TlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly9l
bmlnbWFpbC5tb3pkZXYub3JnCgppRVlFQVJFQ0FBWUZBa3FWNE9rQUNna1F1VFhQVW5BNWVN
S1hCQUNmZVBCakRyVGNiYSs0cFFNT0V5bDdJYUxNCjJQVUFuMTlGWDh6czVpS2FRUEplL3Zp
NUhrcjlnaFgrCj00ZVFzCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQoK
--------------040504060602070908000807--

--------------enigF8887F9F24736E2AEC37A7C0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqV4ZsACgkQuTXPUnA5eMKikgCeOa++IJYMe3/KS2IgpZRFLV1S
AlcAn1cuTmqy23Jtc2Y5Z5wDnCsNlNNm
=IQez
-----END PGP SIGNATURE-----

--------------enigF8887F9F24736E2AEC37A7C0--