Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 2
    I've heard that setting LD_LIBRARY_PATH is an evil hack. Does this apply here as well, or have I misunderstood? Commented Feb 10, 2016 at 13:59
  • 3
    All the issues with setting LD_LIBRARY_PATH apply. yes, it is, or can be, an evil hack. sometimes evil hacks are necessary to achieve particular goals...the crucial thing when breaking "rules" is to know them well enough to know what they're designed to save you from, and exactly why you need to break them in this particular case, and what the risks are or might be. Commented Feb 10, 2016 at 23:42
  • I just had to install an independent program (zoom), so first I tried the 2nd option (dpkg-deb -x to a local dir). Worked like a charm. I did not have to do any LD_LIBRARY_PATH hacks. Even if I have to, I would do it in the same command line so as not to affect the global settings (for example $ LD_LIBRARY_PATH=/home/usr1/zoom/opt/zoom:/home/usr1/zoom/opt/zoom/zoom ZoomLauncher). Commented Sep 14, 2018 at 13:29
  • you only need to set LD_LIBRARY_PATH if one or more the packages you want to install provides any shared libraries. If it's just executables & data & docs & config files etc, then it can use the system libraries. Commented Sep 14, 2018 at 23:40
  • can you provide a concrete example? Commented Dec 6, 2022 at 1:58