I disagree. It wouldn't be found in a Xen installation would it. And if you want to use just remote URIs then ' installing this one without them is perfectly reasonable'.
Would it not be more appropriate to split libvirt-bin into two packages - one of which is core and can be used for remote URI, testing and Xen installation and the other which is tied more closely to your ubuntu KVM strategy. There seems to be an increasing rigidity creeping into the Ubuntu mindset. On 7 April 2010 02:24, Mathias Gug <math...@ubuntu.com> wrote: > According to the Debian policy: > > Recommends > > This declares a strong, but not absolute, dependency. > > The Recommends field should list packages that would be found > together with this one in all but unusual installations. > > Suggests > > This is used to declare that one package may be more useful with one > or more others. Using this field tells the packaging system and the user > that the listed packages are related to this one and can perhaps enhance > its usefulness, but that installing this one without them is perfectly > reasonable. > > It seems that Recommends is the best option for qemu-kvm. > > Note that you can use the --no-install-recommends option with installing > the libvirt package. > > ** Changed in: libvirt (Ubuntu) > Importance: Undecided => Wishlist > > ** Changed in: libvirt (Ubuntu) > Status: New => Won't Fix > > -- > libvirt packages should not Recommend hypervisor packages > https://bugs.launchpad.net/bugs/556312 > You received this bug notification because you are a direct subscriber > of the bug. > -- Neil Wilson -- libvirt packages should not Recommend hypervisor packages https://bugs.launchpad.net/bugs/556312 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
