← Back to issue list

Need a way to set LD_LIBRARY_PATH

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1667148
Type
issue
State
closed
Author
~michihenning
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Closed without resolution or comments. The request to directly set LD_LIBRARY_PATH via YAML environment variables was not implemented and the issue appears abandoned.

Suggested action:

No scores available.

Issue body

I can't come up with a reasonable way to set LD_LIBRARY_PATH to include additional locations. In the yaml, I tried environment: LD_LIBRARY_PATH: lib/storage-framework/provider But, when running the corresponding binary, this results in: /snap/storage-framework/x1/command-storage-framework-registry.wrapper: 5: export: :/snap/storage-framework/x1/lib:/snap/storage-framework/x1/usr/lib:/snap/storage-framework/x1/usr/lib/x86_64-linux-gnu: bad variable name Interestingly, this works: environment: FOO: BAR I don't know what's special about LD_LIBRARY_PATH in this context. I worked around the problem by using a script that sets LD_LIBRARY_PATH before running the binaries. But that has it's own set of problems: - It's a round-about way of achieving something that should be dead simple - We have the snapcraft-generated wrapper script, which then calls my script. My script calls desktop-launch (because we use ubuntu-app-platform), which then execs the real binary. That's *three* shells being forked/exec'd to start a process! It would be *really*, *really* nice to be able to just set LD_LIBRARY_PATH directly from the yaml.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution or comments. The request to directly set LD_LIBRARY_PATH via YAML environment variables was not implemented and the issue appears abandoned.
qwen/qwen3.6-35b-a3b Closed without resolution. The snapcraft yaml limitation preventing direct LD_LIBRARY_PATH configuration remains unresolved, requiring manual wrapper scripts as a workaround.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution or comments. Direct YAML support for LD_LIBRARY_PATH remains unsupported, leaving users to rely on wrapper script workarounds.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1665 patchelf to ignore LD_LIBRARY_PATH snapcraft closed Closed without comments or labels. No resolution or implementation details were provided, indicating the request was abandoned.
74%