From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: 27438@debbugs.gnu.org
Subject: [bug#27438] [PATCH] Specify native search path for all ruby packages
Date: Wed, 21 Jun 2017 15:12:18 +0200 [thread overview]
Message-ID: <878tkliix9.fsf@gnu.org> (raw)
In-Reply-To: <bed7e0fa-4c03-ae62-86d1-b4cd4d04b150@uq.edu.au> (Ben Woodcroft's message of "Wed, 21 Jun 2017 21:47:54 +1000")
Ben Woodcroft <b.woodcroft@uq.edu.au> skribis:
> On 21/06/17 16:36, Christopher Baines wrote:
>> Without specifying this explicitly in each definition, the GEM_PATH is
>> inherited and the version is that of the inherited package.
>>
> I'm not sure if this is by design, but the version of the gems folder
> is embedded in the build of each rubygem e.g. 'ruby-hoe' includes
> /gnu/store/d867l5i2dqd5qnq4qlsrcwwb0x3443fl-ruby-hoe-3.16.0/lib/ruby/gems/2.4.0
Or should the search path spec include both lib/ruby/gems/2.2.0 and
lib/ruby/gems/2.4.0, in this order?
Ludo’, who has no experience with Ruby.
next prev parent reply other threads:[~2017-06-21 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 6:36 [bug#27438] [PATCH] Specify native search path for all ruby packages Christopher Baines
2017-06-21 6:38 ` [bug#27438] [PATCH 1/3] gnu: ruby-1.8: Fix search path specification Christopher Baines
2017-06-21 6:38 ` [bug#27438] [PATCH 2/3] gnu: ruby-2.2: " Christopher Baines
2017-06-21 6:38 ` [bug#27438] [PATCH 3/3] gnu: ruby-2.3: " Christopher Baines
2017-06-21 11:47 ` [bug#27438] [PATCH] Specify native search path for all ruby packages Ben Woodcroft
2017-06-21 13:12 ` Ludovic Courtès [this message]
2017-06-22 5:27 ` Ben Woodcroft
2017-06-22 5:40 ` Christopher Baines
2017-07-16 17:37 ` Christopher Baines
2017-07-16 17:40 ` [bug#27438] [PATCH] guix: build: ruby-build-system: Install to the vendor directory Christopher Baines
2017-07-19 23:39 ` [bug#27438] [PATCH] Specify native search path for all ruby packages Ben Woodcroft
2017-07-22 10:06 ` Christopher Baines
2017-08-05 3:59 ` Ben Woodcroft
2017-08-05 21:55 ` Christopher Baines
2017-08-06 7:17 ` Ben Woodcroft
2017-06-21 13:10 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tkliix9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27438@debbugs.gnu.org \
--cc=b.woodcroft@uq.edu.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).