[scl.org] SCL packages and linker paths

[Will Yardley]

On Tue, Jul 28, 2015 at 02:33:08PM +0200, Miroslav Suchý wrote:
> Dne 27.7.2015 v 02:11 Noah Kantrowitz napsal(a):

> > Hi there. I'm working on some Chef tooling for Python and Ruby to
> > allow swapping runtimes in a modular way. The easiest way to do this
> > is to pass through different paths to a Python binary. For system
> > packages, it uses /usr/bin/python while for SCL it uses
> > /opt/rh/<something/root/usr/bin/python. This means not using the
> > `scl enable` command though, which presents a problem. Most of the
> > environment variables set in the enable files are nice but not
> > required, but LD_LIBRARY_PATH presents an issue. Because the SCL
> > binaries do not have an RPATH in their header, they simply fail to
> > start in most cases, or locate the wrong libraries if there is
> > overlap with system packages. Is there a compelling reason to not
> > bake this RPATH into the SCL binaries directly?
 
> The easiest way is to create wrapper.
> 
> I created one for ruby193 SCL:
>   http://koji.katello.org/koji/buildinfo?buildID=4636

That may be the "easiest" way, but doesn't seem very clean. It would be
much better if they're built in such a way that tools can use
/path/to/foo in the shebang line. Since virtually everything except the
LD_LIBRARY_PATH are compiled in, seems like the solution above would
allow this to work.

w