qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <claudio.fontana@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QEMU website (wiki) improvements
Date: Mon, 2 Mar 2015 15:31:39 +0100	[thread overview]
Message-ID: <54F4744B.2020004@huawei.com> (raw)
In-Reply-To: <CAFEAcA8+u28-J1=VM9g=uUDMFDh5m_JviBywtZdJt7Uu2tgLWw@mail.gmail.com>

On 02.03.2015 15:01, Peter Maydell wrote:
> On 2 March 2015 at 22:36, Claudio Fontana <claudio.fontana@huawei.com> wrote:
>> Another suggestion for the QEMU website: improve the testing page,
>> adding at least one ready-to-run image for smoke testing for each supported arch.
>>
>> http://wiki.qemu.org/Testing
> 
> The thing about providing Linux system images is the awkwardness of
> satisfying the GPL source-code-provision requirements for everything
> in them... It would be nice if new images came with complete
> how-to-reproduce-this-image information.
> 
> -- PMM
>

What about adding FreeBSD Sparc64 and x86_64 images, with the minimal amount of GPL packages required?
We could then add to the same testing pages the exact sources of the packages for download, which should not be that many,
according to:

https://wiki.freebsd.org/GPLinBase

just an idea...

Claudio

  reply	other threads:[~2015-03-02 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 15:29 [Qemu-devel] QEMU website (wiki) improvements Stefan Weil
2015-03-02 13:36 ` Claudio Fontana
2015-03-02 14:01   ` Peter Maydell
2015-03-02 14:31     ` Claudio Fontana [this message]
2015-03-02 22:12 ` Stefan Hajnoczi
2017-01-22 15:19   ` Stefan Weil
2017-01-23 10:28     ` Stefan Hajnoczi
2017-03-28 19:37       ` Stefan Weil
2017-07-01 17:35       ` Stefan Weil

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=54F4744B.2020004@huawei.com \
    --to=claudio.fontana@huawei.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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;
as well as URLs for NNTP newsgroup(s).