All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xensource.com,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH 4/9] raisin: add a component to build qemu_traditional
Date: Wed, 15 Apr 2015 17:21:38 +0100	[thread overview]
Message-ID: <552E9012.4080705@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1504151708040.7690@kaball.uk.xensource.com>

On 04/15/2015 05:11 PM, Stefano Stabellini wrote:
> On Wed, 15 Apr 2015, Ian Campbell wrote:
>> On Wed, 2015-04-15 at 16:49 +0100, Andrew Cooper wrote:
>>>>> It would be nice if there was a --wtih-system-qemu-trad= option, but
>>>>> that has been looked upon unfavourably by the maintainers.
>>>> Thanks for feedback!!
>>>> I think Raisin needs something like --with-system-qemu-trad=, so if Xen
>>>> doesn't provide it, we'll have to carry a patch in Raisin to do it.
>>>>
>>>> Do you have a link to the discussion or previously rejected patch?
>>>
>>> I am not sure that there was ever a patch - it may have been a
>>> discussion I had with ijc in person.
>>
>> Possibly I can't remember myself either.
>>
>>> I would be +1 for a --with-system-qemu-trad= option to mirror the
>>> --with-system-qemu, especially as I am now not the only advocate of one.
>>
>> In a pre-raisin world I suppose I thought it didn't make too much sense
>> to go through that churn if we weren't going to stop _all_
>> cloning/downloading from within xen.git.
>>
>> Personally I would have considered qemu-trad very much part of the long
>> tail wrt moving things out of xen.git, but anyway.
>>
>> I'd like to see raisin used/supported by osstest before we start
>> accepting thoe sorts of xen.git patches being suggested here.
> 
> I think we'll have to carry those patches in Raisin anyway, otherwise
> how are we supposed to be able to build xen 4.5? I don't think is
> reasonable to be able to build only 4.6 onward.

Why isn't that reasonable?  It's a completely new tool.

Speaking of which -- are we going to try to make any version of raisin
build any random version of Xen, or are we going to have "releases" of
raisin (and subsequent branches and tags in the raisin.git tree) for
each version we want to support?

 -George

  parent reply	other threads:[~2015-04-15 16:21 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 15:14 [PATCH 0/9] raisin: introduce qemu and qemu-traditional Stefano Stabellini
2015-04-15 15:14 ` [PATCH 1/9] raisin: do not clean before build Stefano Stabellini
2015-04-15 15:26   ` George Dunlap
2015-04-15 15:14 ` [PATCH 2/9] raisin: use timestamps for dpkg Version to avoid versions that start with letters Stefano Stabellini
2015-04-15 15:34   ` Olaf Hering
2015-04-15 15:40     ` Stefano Stabellini
2015-04-15 15:14 ` [PATCH 3/9] raisin: add QEMU upstream component Stefano Stabellini
2015-04-15 19:05   ` Julien Grall
2015-04-16  9:51     ` Stefano Stabellini
2015-04-16  9:54       ` George Dunlap
2015-04-16 10:29         ` Stefano Stabellini
2015-04-16 10:49         ` Julien Grall
2015-04-15 15:14 ` [PATCH 4/9] raisin: add a component to build qemu_traditional Stefano Stabellini
2015-04-15 15:26   ` Andrew Cooper
2015-04-15 15:44     ` Stefano Stabellini
2015-04-15 15:49       ` Andrew Cooper
2015-04-15 15:51         ` George Dunlap
2015-04-15 15:58         ` Ian Campbell
2015-04-15 16:11           ` Stefano Stabellini
2015-04-15 16:15             ` Ian Jackson
2015-04-15 16:26               ` Ian Campbell
2015-04-15 17:41                 ` Stefano Stabellini
2015-04-16  8:45                   ` Ian Campbell
2015-04-16  9:54                     ` Stefano Stabellini
2015-04-16 10:10                       ` Ian Campbell
2015-04-16 10:25                         ` Stefano Stabellini
2015-04-16 10:39                           ` George Dunlap
2015-04-16 10:48                             ` Ian Campbell
2015-04-16 10:55                               ` Stefano Stabellini
2015-04-16 10:59                                 ` George Dunlap
2015-04-16 11:15                           ` Ian Jackson
2015-04-15 16:21             ` George Dunlap [this message]
2015-04-15 17:42               ` Stefano Stabellini
2015-04-16  8:47                 ` Ian Campbell
2015-04-16  9:53                   ` Stefano Stabellini
2015-04-16 10:09                     ` Ian Campbell
2015-04-15 16:24             ` Ian Campbell
2015-04-16 16:03     ` Stefano Stabellini
2015-04-17  8:41       ` Ian Campbell
2015-04-15 15:14 ` [PATCH 5/9] raisin: remove UPSTREAM_ for URL and REVISION variables Stefano Stabellini
2015-04-15 15:14 ` [PATCH 6/9] raisin: add some debugging output for VERBOSE=1 Stefano Stabellini
2015-04-15 15:14 ` [PATCH 7/9] raisin: remove unneeded chmod +x xencommons xendomains xen-watchdog Stefano Stabellini
2015-04-15 15:31   ` George Dunlap
2015-04-15 15:14 ` [PATCH 8/9] raisin: rename MAKE to RAISIN_MAKE Stefano Stabellini
2015-04-15 15:15 ` [PATCH 9/9] raisin: add $INST_DIR/usr/lib64 to LDFLAGS for QEMU and Libvirt Stefano Stabellini
2015-04-15 15:42   ` George Dunlap
2015-04-15 15:43 ` [PATCH 0/9] raisin: introduce qemu and qemu-traditional George Dunlap
2015-04-15 15:57   ` Stefano Stabellini

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=552E9012.4080705@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.