Joe, I'm sorry. For some reason, I'm not getting the emails from this bug.
> Are those paths build time or runtime paths?
Runtime paths.
> Are those paths needed for the snap's app(s)?
Usually.
> Are the paths included when the dependency is already installed on the builder's system versus being installed during the 'stage-packages' handling code?
They are only included when the dependency is already installed on the builder's system.
(This is a snapcraft feature, this isn't something I'm doing myself. Snapcraft does some ldd logic or something on the binaries.)
==
@sergio, you said "The solution IMO is to not conflate LD_LIBRARY_PATH we generate with the one from the machine built and only include the ones we control." -- I don't follow.
Joe, I'm sorry. For some reason, I'm not getting the emails from this bug.
> Are those paths build time or runtime paths?
Runtime paths.
> Are those paths needed for the snap's app(s)?
Usually.
> Are the paths included when the dependency is already installed on the builder's system versus being installed during the 'stage-packages' handling code?
They are only included when the dependency is already installed on the builder's system.
(This is a snapcraft feature, this isn't something I'm doing myself. Snapcraft does some ldd logic or something on the binaries.)
==
@sergio, you said "The solution IMO is to not conflate LD_LIBRARY_PATH we generate with the one from the machine built and only include the ones we control." -- I don't follow.