John Summerfield wrote:
Richard W.M. Jones wrote:
> John Summerfield wrote:
>> virtinst--devel/virtinst/ParaVirtGuest.py: cmd =
>> ["/usr/bin/virsh", "console", "%s"
%(self.domain.ID(),)]
>>
>> Surely, the location of executable components should not be
>> hard-coded in the source tree. I could live with it, grudgingly, if
>> it was set at configure time.
>
> Agreed -- this is simply a bug in virt-manager.
There are a few other places the virt* programs have fixed ideas about
where stuff must be:
[summer@potoroo virt]$ find * -type f -exec grep -HE '/usr/(|s)bin' {}
\; | grep -Ev '/usr/bin/(perl|python)'
By and large these are not bugs. It would only be a bug if an installed
program contains a hard-coded path, and the path is not discovered by
(eg) ./configure, and there is no way around the hard-coded path at
runtime, and the user could conceivably want to use a different binary.
Rich.
--
Emerging Technologies, Red Hat -
http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903