[debbugs-tracker] bug#27438: closed ([PATCH] Specify native search path for all ruby packages)

[GNU bug Tracking System]

Your message dated Sun, 14 Jan 2018 22:24:17 +0000
with message-id <address@hidden>
and subject line Re: [bug#27438] [PATCH] guix: build: ruby-build-system: 
Install to the vendor directory
has caused the debbugs.gnu.org bug report #27438,
regarding [PATCH] Specify native search path for all ruby packages
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
27438: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27438
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] Specify native search path for all ruby packages Date: Wed, 21 Jun 2017 07:36:41 +0100 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0

Without specifying this explicitly in each definition, the GEM_PATH is
inherited and the version is that of the inherited package.

signature.asc
Description: OpenPGP digital signature

--- End Message ---

--- Begin Message --- Subject: Re: [bug#27438] [PATCH] guix: build: ruby-build-system: Install to the vendor directory Date: Sun, 14 Jan 2018 22:24:17 +0000 User-agent: mu4e 0.9.18; emacs 25.3.1

Ben Woodcroft <address@hidden> writes:

> Hi Chris,
>
>
> On 18/12/17 00:19, Christopher Baines wrote:
>> Hey,
>>
>> It's been a while since I looked at this, but I think it's still
>> relevant.
>>
>> As a reminder, currently the search paths for the Ruby packages in Guix
>> are a bit off [1], which makes it difficult to use Ruby gems with
>> different versions of Ruby.
>>
>> Rubygems by default installs gems to directories specific to the version
>> of Ruby, and this can be helpful when managing multiple versions of Ruby
>> and different sets of gem packages in a shared directory, but with Guix,
>> this isn't necessary, as the store can be used.
>>
>> Ruby/Rubygems supports installing gems in to a vendor directory, which
>> is for gems installed by the package system [2]. While Guix blurs the
>> lines between the "package system" and the "user", using this vendor
>> directory might come in useful.
>>
>> I've attached an updated patch, and successfully built every Ruby
>> package [3], as well as all of the packages that were changed in the
>> patch. The only failure was ruby-pg, which failed to build before this
>> patch.
>>
>> Ideally when using specific versions of ruby, any gems that need to be
>> build with that version of ruby, would be. While this change doesn't do
>> that, it does simplify the search paths of ruby packages and the
>> packages for ruby gems.
>>
>> Reading the bug report again, I think there was nearly consensus about
>> merging this, but I wanted to check if anyone has any comments or
>> experience with Ruby/Rubygems before merging this?
> I think go ahead with this one. It will be useful particularly when we
> update ruby to 2.5.

Great, I've pushed this along with the other ruby build system change.

Thanks for reviewing,

Chris

signature.asc
Description: PGP signature

--- End Message ---