Including shared libraries in a package

[Stephan Hermann]

Hi Brian,


On Tue, 6 Jan 2009 19:13:02 -0500
"Brian Thomason" <brian.thomason at canonical.com> wrote:

> [...]
>
> Now that I have bored you sufficiently, my question really is: Is
> there a better way to meet their needs that also better follows our
> standard practices?

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>}

and then a symlink from 
	/opt/<vendor>/<application>-<version>/
to
	/opt/<vendor>/<application>/

when ACKed by sysadmin.

Why?

It helps me to separate the (mostly) closed source crap from the
standard OS (with this I mean the ubuntu server installation with the
shipped software). I can deal with updates/upgrades more smoothly and
know that those packages are not touching or installing anything on my
standard server installation.

Regards,

\sh

-- 
Stephan '\sh' Hermann		| OSS Developer & SysAdmin 
JID: sh at linux-server.org	| http://www.sourcecode.de/ 
GPG ID:0xC098EFA8		| 3D8B 5138 0852 DA7A B83F  
				| DCCB C189 E733 C098 EFA8