unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Add yaggo.
Date: Thu, 25 Jun 2015 18:25:33 -0400	[thread overview]
Message-ID: <CAJ=RwfZUs+iyAnPxKmg3_UwCxdm7onQWDnX0B6o==L8fnoGjYw@mail.gmail.com> (raw)
In-Reply-To: <558B4025.7020804@uq.edu.au>

On Wed, Jun 24, 2015 at 7:41 PM, Ben Woodcroft <b.woodcroft@uq.edu.au> wrote:
>
>
> On 24/06/15 22:19, Thompson, David wrote:
>>
>> Perhaps ruby should
>> be a propagated input for packages with ruby executables, or scripts
>> could be wrapped in another script that set the correct environment
>> variables.
>
> A naive question - I don't believe that this is required for e.g. python
> packages that have executables and the somewhat analogous PYTHONPATH. Why is
> Ruby different?

The Python build system creates wrappers around all executables that
sets the proper PYTHONPATH.  I'm not a big fan of this approach, but
something similar will probably need to be done for Ruby if we can't
find a better way.

- Dave

  reply	other threads:[~2015-06-25 22:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  4:35 [PATCH] Add yaggo Ben Woodcroft
2015-06-24  5:51 ` Pjotr Prins
2015-06-24 12:32   ` Thompson, David
2015-06-24 13:05     ` Ricardo Wurmus
2015-06-24 19:23     ` Pjotr Prins
2015-06-25 22:47       ` Thompson, David
2015-06-26  6:56         ` Ricardo Wurmus
2015-06-26  7:40           ` Pjotr Prins
2015-06-24 12:19 ` Thompson, David
2015-06-24 23:41   ` Ben Woodcroft
2015-06-25 22:25     ` Thompson, David [this message]
2015-07-05  7:33 ` Mark H Weaver
2015-07-05 11:33   ` Ben Woodcroft

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='CAJ=RwfZUs+iyAnPxKmg3_UwCxdm7onQWDnX0B6o==L8fnoGjYw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.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.
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).