Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a set of libraries and some apps that depend on it. Some of these libraries names might conflict with already installed libraries.

The easiest way for me to deploy them would be

  • Install the libraries in a fixed-path "/usr/local/[my-firm]/lib"
  • Compile my apps with a rpath pointing to this path
  • My apps' installer can tell if the libraries are installed by looking at something like "/usr/local/[my-firm]/libversion"

What do you think about it ?

Is installing the libraries in a fixed path acceptable ?


I should add that I wish to be able to ship my libraries and my apps independently.

share|improve this question
up vote 2 down vote accepted

If the libraries you install are specific for your application and may conflict with system libraries installed then I would recommend setting up a structure like this:




This way you can deploy at will separately from others and not affect anything that someone else might require and you can force your application to look at those paths if you choose.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.