WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

RE: [Xen-API] Building with source on github (and pull requests)

To: 'Anil Madhavapeddy' <anil@xxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
Subject: RE: [Xen-API] Building with source on github (and pull requests)
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Fri, 17 Dec 2010 14:22:59 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Magnus Therning <Magnus.Therning@xxxxxxxxxxxxx>, Xen-API List <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 17 Dec 2010 06:23:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <56DDEF31-B163-4C95-BAC8-918256032537@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <20101216104129.GB2383@xxxxxxxxxxxxxxxxxxxxxx> <20101216165018.GO2754@xxxxxxxxxxx> <56DDEF31-B163-4C95-BAC8-918256032537@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acud1cD+YM/A0LqOSE2kVuEZ/dY42AAHxsSQ
Thread-topic: [Xen-API] Building with source on github (and pull requests)
> Unfortunately, only some of the repositories required to do a full XCP
> ISO build appear to be open-source at the moment, so it'll take more
> than a tutorial...

This is true. I think we're missing a bunch of unpackaged dom0 scripts (we 
really need to package those) plus vncterm plus the host installer-- can you 
think of anything else? We should probably consider dropping vncterm and 
replacing it with qemu's text console. That would leave the scripts + the 
installer.

I think if we get the rough shape of an ideal XCP ISO build mapped out 
(something like: use 'mock' to generate binary RPMs from SRPMs; use 'rpmchroot' 
+ 'mkisofs' + ? to build CD) then the act of "debugging" that would cause us to 
tidy up, package and publish all the remaining bits 'n pieces IYSWIM :)

Cheers,
Dave

> 
> Anil
> 
> 
> 
> >
> > -- Pasi
> >
> >> In the process I've built some new RPMs for some of the ocaml bits,
> Jon, where
> >> should I put them so that you can update the yum repo you built?
> >>
> >> I've also made some minor changes to xen-api-libs and xen-api.  I've
> put those
> >> changes into pull requests on each project [2] and [3].
> >>
> >> Cheers,
> >> M
> >>
> >> [1] https://github.com/xen-org
> >> [2] https://github.com/xen-org/xen-api-libs/pulls
> >> [3] https://github.com/xen-org/xen-api/pulls
> >> --
> >> Magnus Therning
> magnus.therning@xxxxxxxxxx
> >> XenServer Security Lead
> >>
> >> There does not now, nor will there ever, exist a programming
> language
> >> in which it is the least bit hard to write bad programs.
> >>     -- Flon's Axiom
> >>
> >>
> >> Perl is another example of filling a tiny, short-term need, and then
> >> being a real problem in the longer term.
> >>     -- Alan Kay
> >>
> >> _______________________________________________
> >> xen-api mailing list
> >> xen-api@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/mailman/listinfo/xen-api
> >
> > _______________________________________________
> > xen-api mailing list
> > xen-api@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/mailman/listinfo/xen-api
> >
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api