[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Add yaggo.
From: |
Thompson, David |
Subject: |
Re: [PATCH] Add yaggo. |
Date: |
Thu, 25 Jun 2015 18:25:33 -0400 |
On Wed, Jun 24, 2015 at 7:41 PM, Ben Woodcroft <address@hidden> 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
- [PATCH] Add yaggo., Ben Woodcroft, 2015/06/24
- Re: [PATCH] Add yaggo., Pjotr Prins, 2015/06/24
- Re: [PATCH] Add yaggo., Thompson, David, 2015/06/24
- Re: [PATCH] Add yaggo., Ricardo Wurmus, 2015/06/24
- Re: [PATCH] Add yaggo., Pjotr Prins, 2015/06/24
- Re: [PATCH] Add yaggo., Thompson, David, 2015/06/25
- Re: [PATCH] Add yaggo., Ricardo Wurmus, 2015/06/26
- Re: [PATCH] Add yaggo., Pjotr Prins, 2015/06/26
Re: [PATCH] Add yaggo., Thompson, David, 2015/06/24