John Summerfield wrote:
> Richard W.M. Jones wrote:
>> 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.
>
> Thanks Rich.
> I am unfamiliar with the tools I need to put that statement to the test.
> INSTALL says to run ./configure, but there is no ./configure to run.
>
> The website does say how to get the source with hg, and how to submit
> changes, but I can't see how to go from the checkout to building and
> installing.
>
> Where is the documentation?
>
> I do want to use alternative binaries (but then again I don't), but I do
> not wish to replace any standard part of F8.
>
>
If you are trying to build virt-manager, run ./autogen.sh that comes with the
source: this will build 'configure'. You will probably need to install a few
things in order to build it like intltool and automake.
- Cole
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
