[Pkg-xen-devel] Re: [Pkg-xen-changes] r19 - in trunk/debian: . patches

[Jeremy T. Bouse]

    It is just my opinion that it is a better way. Both of them provide
the xen-hypervisor albeit slightly different hardware but provide the
same function. Right now we only have the xen meta-package and xen-utils
that depend on a xen-hypervisor (regardless of PAE or not) but anything
else that might be packaged which would require a xen-hypervisor might
use it as well and is easier to have them only need the one depend
rather than both. I would figure that the vm-tools that were previously
mentioned might require that a hypervisor be available and this would be
the most ideal way for that to be determined and depended on.

    I'm always open to comments but that seemed like the most logicial
way to go with it.

Guido Trotter wrote:

>On Sat, Feb 18, 2006 at 11:44:46PM +0100, Ralph Passgang wrote:
>
>Hi,
>
>  
>
>>I thought maintaining the "xen-hypervisor | xen-hypervisor-pae" as dependency 
>>would be easier then doing this with the "Prvoide"-tag, but if that was just 
>>me, feel free to change it again. it's absolutly ok for me.
>>
>>    
>>
>
>For me it's the same, as for you, and I actually did it the same way, before...
>It seems like Jeremy preferred the other one, though, so I asked...
>
>Guido
>
>
>_______________________________________________
>Pkg-xen-devel mailing list
>Pkg-xen-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel
>
>  
>