Bug#410039: No /usr/lib/xen folder so it's confusing other packages

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Thomas Goirand <thomas@goirand.fr> writes:

> Goswin von Brederlow wrote:
>> Thomas Goirand <thomas@goirand.fr> writes:
>> 
>>> Goswin von Brederlow wrote:
>>>> The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
>>>> can be installed and they are incompatible with each other. If each
>>>> one contained /usr/lib/python/xen then the packages would have to
>>>> conflict.
>>> I understood that, for sure!
>>>
>>>> What you need is a common package that contains wrapper scripts in
>>>> /usr/lib/python/xen that will pick the right
>>>> /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
>>>> version.
>>>>
>>>> Maybe xen-utils-common is what you should be using?
>>> Maybe a script run at startup could check for the xen version that is
>>> running and make the appropriate symlink? Sure that could be in a
>>> xen-common package, for example... Is that what xen-utils-common does?
>>>
>>> Thomas
>> 
>> /usr is (potentially) read-only. You can only write there during
>> install time which is not enough. You would have to put a static link
>> to /var/lib/xen and then have a dynamic link there or something.
>> 
>> MfG
>>         Goswin
>
> Then what's the solution???
>
> Thomas

Beats me. The xen maintainer(s) have to make a choice there.

MfG
        Goswin