From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <ak@suse.de>
Subject: Re: tidy up requested
Date: 11 Aug 2005 01:08:04 +0200
Message-ID: <p73acjp4ch7.fsf@verdi.suse.de>
References: <E1E2tgW-0006vl-00@mta1.cl.cam.ac.uk>
	<200508102321.49800.mark.williamson@cl.cam.ac.uk>
	<42FA8777.7000106@lanl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <42FA8777.7000106@lanl.gov>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ronald G Minnich <rminnich@lanl.gov>
Cc: xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
List-Id: xen-devel@lists.xenproject.org

Ronald G Minnich <rminnich@lanl.gov> writes:

> So I can not convince you to allow multiple versions of xen on one machine?
> 
> People who are using 2.0 and porting to 3.0 (like me and newsham and
> ...) could sure use that setup!

The standard way to do that would be to support $(prefix) properly.
So you end up with $(prefix)/lib/xen ..  $(prefix)/sbin $(prefix)/etc ...
Like /opt/xen2/.... /opt/xen3/... etc.

The problem would be to make sure that all tools that read files
or execute programs know about the prefix.

-Andi