From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Foreign packages (formerly Re: [PATCH] gnu: Add ruby-nokogiri)
Date: Sun, 21 Feb 2016 13:02:31 +0100 [thread overview]
Message-ID: <20160221120231.GA29139@thebird.nl> (raw)
In-Reply-To: <87io1i48k5.fsf@elephly.net>
On Sun, Feb 21, 2016 at 12:16:58PM +0100, Ricardo Wurmus wrote:
> > So any Ruby interpreter 2.2.x version will share the same gems. It is not
> > necessarily a problem because the Ruby world is built around this
> > assumption. But when I look at developer support and reproducibility I
> > don't like it much. You can have software running with different Ruby
> > interpreters under the hood - and you won't know it.
>
> Do they really reference different variants of Ruby in the background?
Potentially: when you have a gem already installed and you update Ruby
to a newer version, you can run the old gem against the newer Ruby
provided it looks in the profile path for modules.
> The ruby-build-system adds the “ruby” package only to the build inputs.
> I don’t have different “ruby-*” packages in my store right now (after
> “guix gc”), so I cannot verify this myself. I would be interested to
> know if references to the “ruby” package are actually retained when
> building, say, “ruby-nokogiri”.
Ruby is an input in the build system, right? After that...
> I haven’t thought enough about this to have an opinion about this.
> Generally, though, I dislike to use environment variables to point the
> interpreter to a prefix where all libraries can be found. I think that
> it’s up to the libraries themselves to find their dependencies (like
> it’s done with RUNPATH).
You are right. The same holds for Guile, python, perl, R and Ruby at
this point.
I think it would be OK to have a profile for every Ruby with libs. The
main problem here is that ruby interpreters can get mixed in with
existing (installed) modules.
I think Dave has pointed this out in the past.
Pj.
prev parent reply other threads:[~2016-02-21 12:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 13:09 [PATCH] gnu: Add ruby-nokogiri Pjotr Prins
2015-07-13 13:24 ` Ricardo Wurmus
2015-07-14 9:06 ` Pjotr Prins
2015-07-14 14:25 ` Ricardo Wurmus
2016-02-17 22:37 ` Pjotr Prins
2016-02-17 23:05 ` Ben Woodcroft
2016-02-18 6:25 ` Foreign packages (formerly Re: [PATCH] gnu: Add ruby-nokogiri) Pjotr Prins
2016-02-21 11:16 ` Ricardo Wurmus
2016-02-21 11:50 ` Ben Woodcroft
2016-02-21 12:05 ` Pjotr Prins
2016-02-21 17:22 ` Foreign packages and reproducibility " Pjotr Prins
2016-02-21 17:31 ` Pjotr Prins
2016-02-22 12:51 ` Pjotr Prins
2016-02-23 18:52 ` Pjotr Prins
2016-03-02 10:33 ` Ricardo Wurmus
2016-03-02 18:50 ` Pjotr Prins
2016-02-21 12:02 ` Pjotr Prins [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
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=20160221120231.GA29139@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).