This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-users] Upgrade Proceedure

To: "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
Subject: RE: [Xen-users] Upgrade Proceedure
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 15 May 2007 16:35:30 +0200
Cc: Mike Wright <xktnniuymlla@xxxxxxxxxxxxxx>, Ian Tobin <itobin@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 May 2007 07:34:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4649C1ED.9030600@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceW/FkBUsjTVClWRde1lOuChCmddgAAWZcg
Thread-topic: [Xen-users] Upgrade Proceedure
[snip a ton of old stuff]
> The INSTALL script you mention works without the build directory in 
> place? That's a bit.... odd.

Not at all. It just takes the files in the "dist" directory (which is a
copy of what's been produced in the individual build directories, e.g.
xen.gz, qemu-dm, vmlinuz, kernel modules, hvmloader, etc, etc), and
copies it out to wherever it goes. Have a look at "dist/install.sh".
It's not complicated, it essentially just copies the files from
"dist/install" to whatever destination you specify (defualt is "/"). 
> > If you're not familiar with it, I'd like to point out that 
> there is a
> > INSTALL script in the distribution directory which can be used to
> > install the resulting product of the make (which is what I described
> > earlier in this thread). 
> >   
> I use Makefiles and RPM's to support full-blown package management, 
> version management, conflict reports, etc., etc., etc. Writing all of 
> that into an installer or uniinstaller script is quite a lot of work.
> I recognize that not every OS has this kind of package 
> management, and 
> prefer to build on the fly.

Great if you have the environment to build the RPM, but if you take the
xen-unstable.hg repo, it doesn't come with spec-files to make RPM's

Obviously, most distributions will use some sort of packagemanagement,
and that solves most of those problems. 


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>