handling interpreters in *-snapper scripts (or snapcraft)

[Ted Gould]

On Mon, 2015-06-15 at 14:03 +0200, Zygmunt Krynicki wrote:

> As an example, to get lxml (pip installable) working you need to
> bundle a few extra libraries that are _not_ handled by anything on the
> python side (no tool automates this). I build a smap with plainbox
> manually by using rpath to show each of the .so files that python
> loads where to load remaining libraries from. It would be very
> beneficial if LD_LIBRARY_PATH was defined by snappy launcher so that
> rpath is not required.


I don't think that the launcher can really set that, as we don't know
exactly what it would be for the particular package. Otherwise we start
to put in magical directory layout things for snaps, which make them
harder to build.

An idea that has been bouncing around is to provide a global environment
setup script for executing in a snap that perhaps could be used for
something like this. You can imagine for instance that the
LD_LIBRARY_PATH could change depending on architecture for a multi-arch
snap.

Ted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150615/3ca36cab/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150615/3ca36cab/attachment.pgp>