[Fedora-xen] virt* source

[Dustin Henning]

	I can't give you any good information on the source and configure options and whatnot, but assuming that there is a hardcoded executable path that doesn't match where you want to build to, wouldn't a hardlink do the trick?  On the other hand, if the install path in the source you want to build is hardcoded, I guess I have no thoughts, but hopefully someone does.
	Dustin

-----Original Message-----
From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield
Sent: Wednesday, January 09, 2008 18:06
To: Fedora Xen
Subject: [Fedora-xen] virt* source


I've checked out the source virt*, but I cannot tell that it's newer 
than I have.

The changelog for virt-manager suggests not.

Mercurial doesn't set file times to those on the server, so they reflect 
when I checked it out rather than what's in the repo.

I planned to build from source and install to /usr/local, but this 
suggests my idea is impractical:

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.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen