From: Raymond Danks <ray.danks@se-eng.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New meta-xen layer
Date: Wed, 27 Jun 2012 11:54:20 -0600 [thread overview]
Message-ID: <4FEB48CC.6050302@se-eng.com> (raw)
In-Reply-To: <CAMKF1spLndPJgVWoHh9Tfs0SRpc=v8PaygUPsoh58ypygi8OvQ@mail.gmail.com>
Thanks very much for the feedback.
On 06/22/2012 06:04 PM, Khem Raj wrote:
> On Fri, Jun 22, 2012 at 2:12 PM, Raymond Danks<ray.danks@se-eng.com> wrote:
>> I have constructed a layer for the purpose of building Xen in OpenEmbedded.
>> Xen is a hypervisor and associated tools running on Linux available as a
>> package in distributions such as Ubuntu and Fedora. It is also modified and
>> included in the rpm-based Xen Cloud Platform distribution and Citrix
>> XenServer.
>>
>> This layer currently includes recipes and recipe modifications for building
>> xen, libvirt, and a minimal xen image that may be used for launching virtual
>> machines via the xl command line interface. This currently targets the x86
>> Xen host (OE target) architecture; development has been done entirely on
>> x86_64.
>>
>> I'm open to receiving feedback, patches and suggestions. Also, I'm curious
>> if this layer may be published to the OpenEmbedded layer index and by what
>> process that should be achieved?
> thanks for doing it and publishing it for community.
> looks pretty good from very quick look at the content
>
> recipes-core/initscripts/ has .swp file committed.
Got it.
> NATIVE_INSTALL_WORKS is probably not needed in recipes
OK. I didn't realize that was depreciated.
> use oe_runmake instead of ${MAKE}
Right. Got it.
> in some recipes you cache ac_cv_* vars you could use
> CACHED_CONFIGUREVARS variable to contain them all instead of putting
> them into EXTRA_OECONF
I didn't notice this method. Thanks for the pointer.
>
> One think I am not sure is of is distro/minimal.conf in there. I dont
> know if you want to have your own distro or not if you do it would be
> nice to separate that out that way other distros can also use this
> layer if they want to.
I've removed it. I'll take a look at the other distros and see if there
is an appropriate place to store this configuration elsewhere.
>
> As long as you maintain the layer in good shape and in alignment with
> other layers you depend on its should be fine and please add the entry
> into LayerIndex on wiki
Yes. And thanks Paul for adding it. This looks good.
>
>> meta-xen|Xen related software||git://git.se-eng.com/meta-xen.git|
>> http://git.se-eng.com/gitweb/?p=meta-xen.git;a=summary|
>>
>> Thanks,
>> Ray
>>
>> Raymond Danks
>> Sage Electronic Engineering, LLC
>> http://www.se-eng.com
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2012-06-27 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 21:12 New meta-xen layer Raymond Danks
2012-06-23 0:04 ` Khem Raj
2012-06-23 10:33 ` Paul Eggleton
2012-12-03 16:39 ` Raymond Danks
2012-12-03 16:58 ` Paul Eggleton
2012-06-27 17:54 ` Raymond Danks [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEB48CC.6050302@se-eng.com \
--to=ray.danks@se-eng.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox