Comment 4 for bug 2011842

Revision history for this message
Michał Sawicz (saviq) wrote :

> Do you think the issue is more about how snapd evaluates environment variables?
>
> I don't think core22's approach to setting this variable is wrong per-say. The `{foo:+bar}` syntax should be posix compliant and I'm not sure of a better snapcraft-only solution for prepending to LD_LIBRARY_PATH.

Well, yes, _if_ you want to use shell substitutions in meta.yaml, SnapD would need to support that explicitly. AFAICS today it only does simple string replacement on `$NAME` and `${NAME}`, nothing fancier. Other than bringing `snapcraft-runner` script back, it's either Snapcraft should stop using that, or SnapD needs to support it… Or maybe just go for `:${LD_LIBRARY_PATH}`, though that may be problematic if it's empty.