[Pkg-xen-devel] Bug#668641: Bug#668641: Bug#668641: Bug#668641: Please add a symlink /usr/lib/xen -> /usr/lib/xen-default

[Bastian Blank]

On Sun, Apr 15, 2012 at 04:43:06AM +0800, Thomas Goirand wrote:
> When designing a software for Xen, we don't want to have to handle a
> specific case for Debian, where /usr/lib/xen is called another way. We
> don't want either to have to patch some upstream code that may be using
> /usr/lib/xen if we want to package it in Debian.

/usr/lib/xen does not describe a public interface.

> Having /usr/lib/xen being the currently running hypervisor is what we
> want here (eg: we might need it at runtime, I don't see any cases where
> we would need it at build time, but I might be wrong).

This is not possible. /usr have to be considered read-only.

> For example, someone might want to access things under /usr/lib/xen/bin,
> or the hvmloader.

hvmloader and other stuff in the configs should be addressed with
relative paths.

>                   Or libxenlight.so

libxenlight.so needs to be the exact match, it does not include an
abiname.

>                                     (which is a public API that isn't in
> /usr/lib, so it might need a RPATH, which here is specific to Debian).

Stuff outside of the normal library search path is not public. So
libxenlight is not a public interface in Debian.

> If you want to achieve this by dropping the use of Xen visioning,

No chance.

Bastian

-- 
Even historians fail to learn from history -- they repeat the same mistakes.
		-- John Gill, "Patterns of Force", stardate 2534.7