From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost ([188.113.84.221]) by mx.google.com with ESMTPS id e21sm1899524bkw.23.2011.08.22.04.31.38 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 22 Aug 2011 04:31:39 -0700 (PDT) From: Gaute Hope To: sup-devel In-reply-to: Subject: Re: [sup-devel] Ruby 1.9.2 Rakefile & LOAD_PATH References: Date: Mon, 22 Aug 2011 13:30:31 +0200 Message-Id: <1314012417-sup-4773@qwerzila> User-Agent: Sup/git Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=-1314012633-989847-19662-7164-2-=" --=-1314012633-989847-19662-7164-2-= Content-Type: multipart/mixed; boundary="=-1314012631-606264-19662-5650-1-=" --=-1314012631-606264-19662-5650-1-= Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Excerpts from Matti Eiden's message of 2011-03-21 19:38:31 +0100: > I posted on sup-talk in last December about an issue in the Rakefile > of sup when it comes to Ruby 1.9.2. The whole thing boils down to > this: https://rails.lighthouseapp.com/projects/8994/tickets/2921 > = > Made merge request @ http://gitorious.org/sup/mainline/merge_requests/1= 1 Hi, this still persists.. here is another alternative using require_relative. Please apply original or my modified, works for me on latest next. Best regards, Gaute --=-1314012631-606264-19662-5650-1-= Content-Disposition: attachment; filename="0001-Rakefile-Require-sup-from-relative-dir.patch" Content-Type: application/octet-stream; name="0001-Rakefile-Require-sup-from-relative-dir.patch" Content-Transfer-Encoding: base64 RnJvbSA1N2FiYTVhMTJiYWY0OGIzMTczYzA1NjhmNjI0ZjdmMTY5MTJiYjM4 IE1vbiBTZXAgMTcgMDA6MDA6MDAgMjAwMQpGcm9tOiBHYXV0ZSBIb3BlIDxl Z0BnYXV0ZS52ZXRzai5jb20+CkRhdGU6IE1vbiwgMjIgQXVnIDIwMTEgMTM6 MjY6MjcgKzAyMDAKU3ViamVjdDogW1BBVENIXSBSYWtlZmlsZTogUmVxdWly ZSBzdXAtKiBmcm9tIHJlbGF0aXZlIGRpcgoKLS0tCiBSYWtlZmlsZSB8ICAg IDQgKystLQogMSBmaWxlcyBjaGFuZ2VkLCAyIGluc2VydGlvbnMoKyksIDIg ZGVsZXRpb25zKC0pCgpkaWZmIC0tZ2l0IGEvUmFrZWZpbGUgYi9SYWtlZmls ZQppbmRleCBkODhmZDhkLi44NjBmNjliIDEwMDY0NAotLS0gYS9SYWtlZmls ZQorKysgYi9SYWtlZmlsZQpAQCAtMzEsOCArMzEsOCBAQCBlbmQKIAogJDou cHVzaCAibGliIgogcmVxdWlyZSAncnVieWdlbXMnCi1yZXF1aXJlICJzdXAt ZmlsZXMiCi1yZXF1aXJlICJzdXAtdmVyc2lvbiIKK3JlcXVpcmVfcmVsYXRp dmUgInN1cC1maWxlcyIKK3JlcXVpcmVfcmVsYXRpdmUgInN1cC12ZXJzaW9u IgogcmVxdWlyZSAncmFrZS9nZW1wYWNrYWdldGFzay5yYicKIAogc3BlYyA9 IEdlbTo6U3BlY2lmaWNhdGlvbi5uZXcgZG8gfHN8Ci0tIAoxLjcuNgoK --=-1314012631-606264-19662-5650-1-=-- --=-1314012633-989847-19662-7164-2-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk5SPdkACgkQCLbddHnmqqYxYQCeOQaxOpesNymxd45ur/eXdvk4 WtoAn3cCKfPAfnlGe0wog5I+g/Fy6Zzv =hU/3 -----END PGP SIGNATURE----- --=-1314012633-989847-19662-7164-2-=--