Including shared libraries in a package

Brian Thomason brian.thomason at
Thu Jan 8 19:54:39 GMT 2009

We certainly encourage the use of /opt with our vendors, and some do use
it.  Others don't, mainly for the same reason they ship their own libraries
- one build for all platforms.  Getting them to change it for Ubuntu means
getting them to change it for all their builds.  Some can be talked into
this easier than others.

Others, like Alfresco, use the paths they do to make integration easier.
(i.e. with Tomcat)

Point taken though, and we will continue to try to get our vendors to use
/opt when possible.

Bet regards,


On Thu, Jan 8, 2009 at 2:45 PM, Luka Renko <lure at> wrote:

> On Thursday 08 January 2009 09:23:50 Stephan Hermann wrote:
> > To be honest, I use some third party non-open-source apps from those
> > vendors and even when I don't like their politics sometimes, I do
> > appreciate when they do not install their libs under /usr/*
> >
> > I do like the way of installing those apps and with their needed libs
> > (I do understand why they need sometimes different libs then we are
> > shipping) under
> >
> /opt/<vendor>/<application>-<version>/{bin,etc,lib,share,<whatever>
> >}
> I would also like to support the use of /opt for partner repository
> packages.
> This makes clear separation and it is anyhow defined in FHS.
> Stephan, I think /opt structure is actually separated on top level,
> therefore
> you have:
> /opt/<xyz>
> /etc/opt/<xyz>
> /var/opt/<xyz>
> More info is available here:
> (or
> Regards,
> Luka
> --
> ubuntu-devel mailing list
> ubuntu-devel at
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the ubuntu-devel mailing list