Hi,
I have just looked at the xen source, because I want to finish my work from
yesterday and have the hypervisor-pae really build & packaged.
It seems so that we have two possibilities to do this:
1) create another dpatch that would patch xen/Makefile in order to have other
filenames for the hypervisor when the pae-flag is set.
the advanced would be, that if we use diffrent filenames for the normal and
the pae-hypervisor we wouldn't need the conflict in debian/control, because
both packages would be installable at the same time, and if the user has for
both hypervisors a seperate menu.lst entry in grub he could easiely switch
between both versions.
2) we do it with hooks in debian/rules and install the pae enabled version not
in debian/install for packaging, but in debian/install-pae or something like
this. by doing this, we could add a second dh_install call just for the
pae-hypervisor (which gets installed from debian/instlall-pae then).
the advantage would be, that no patching of upstream is required, but then we
still need the conflict in debian/control, because both hypervisor would
consist files with exactly the same name.
I would think posiblity no. 1 is the better way to go... If the list agrees, I
will try to create a patch for that today.
when the normal hpyervisor is called: xen-3.0.1.gz (and xen.gz) would it be ok
to call the xen-pae hypervisor: xen_pae-3.0.1.gz (and xen_pae.gz) ?
--Ralph