From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Ruby 1.9.2 Rakefile & LOAD_PATH
Date: Mon, 22 Aug 2011 13:30:31 +0200 [thread overview]
Message-ID: <1314012417-sup-4773@qwerzila> (raw)
In-Reply-To: <AANLkTim7rVtS4+b-Pbv-DLNKYh-bSCjnUT=thDAJJmZM@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
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/11
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
[-- Attachment #1.2: 0001-Rakefile-Require-sup-from-relative-dir.patch --]
[-- Type: application/octet-stream, Size: 627 bytes --]
From 57aba5a12baf48b3173c0568f624f7f16912bb38 Mon Sep 17 00:00:00 2001
From: Gaute Hope <eg@gaute.vetsj.com>
Date: Mon, 22 Aug 2011 13:26:27 +0200
Subject: [PATCH] Rakefile: Require sup-* from relative dir
---
Rakefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Rakefile b/Rakefile
index d88fd8d..860f69b 100644
--- a/Rakefile
+++ b/Rakefile
@@ -31,8 +31,8 @@ end
$:.push "lib"
require 'rubygems'
-require "sup-files"
-require "sup-version"
+require_relative "sup-files"
+require_relative "sup-version"
require 'rake/gempackagetask.rb'
spec = Gem::Specification.new do |s|
--
1.7.6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-08-22 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 18:38 Matti Eiden
2011-08-22 11:30 ` Gaute Hope [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1314012417-sup-4773@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox