From: "Gémes Géza" <geza.gemes@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: raisin and minios stubdom
Date: Thu, 30 Mar 2017 19:42:48 +0200 [thread overview]
Message-ID: <16c8e69b-7076-8ab2-b6ea-29eab52ae278@gmail.com> (raw)
In-Reply-To: <20170327193819.GI19361@char.us.oracle.com>
> On Mon, Mar 27, 2017 at 09:28:14PM +0200, Gémes Géza wrote:
>> Hi,
>>
>> Currently the xen build system has optional support for building a minios
>> (+needed libraries and tools) based stubdom.
>>
>> What is your opinion about moving support for building this into raisin and
>> once that is stable drop support in the xen build system?
> Why? I do like doing 'make' and 'make install' and it doing everything
> for me.
>
>> Cheers,
>>
>> Geza
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> https://lists.xen.org/xen-devel
Because it means that xen build needs to download and build a lot of 3PP
components. Raisin is already designed to do so (it already builds
qemu-xen, qemu-traditional, libvirt and a few others). I think building
anything besides xen proper would fit its scope better.
Cheers,
Geza
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-30 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 19:28 raisin and minios stubdom Gémes Géza
2017-03-27 19:38 ` Konrad Rzeszutek Wilk
2017-03-30 17:42 ` Gémes Géza [this message]
2017-03-31 14:05 ` Konrad Rzeszutek Wilk
2017-03-31 14:15 ` Juergen Gross
2017-04-01 6:19 ` Géza Gémes
2017-04-01 18:00 ` Gémes Géza
2017-04-03 5:20 ` Juergen Gross
2017-04-07 18:54 ` Géza Gémes
2017-04-10 5:05 ` Juergen Gross
2017-04-19 23:33 ` Stefano Stabellini
2017-04-03 11:17 ` George Dunlap
2017-04-03 12:01 ` Wei Liu
2017-04-07 18:29 ` Gémes Géza
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=16c8e69b-7076-8ab2-b6ea-29eab52ae278@gmail.com \
--to=geza.gemes@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.