qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kamil Rytarowski <n54@gmx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] NetBSD maintenance
Date: Tue, 25 Apr 2017 15:49:12 +0200	[thread overview]
Message-ID: <7eea43e9-08d1-256c-a15b-d5b135a0725f@gmx.com> (raw)
In-Reply-To: <CAFEAcA_isLjtq0oZgKTY5J_MStbcENDaWow3kV1bJWpeEBxAzw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]

On 24.04.2017 12:12, Peter Maydell wrote:
> Upstream we're definitely going to drop SunOS/Solaris support unless
> somebody provides us with a machine we can do build/test on.
> DragonFly BSD is in my "let's see if anybody complains" list.
> OpenBSD is also in this "let's see" list but it seems more plausible
> that somebody will complain (and I have a VM setup for it; it
> doesn't pass 'make check' at the moment so the first step there
> will be for somebody to investigate and send fixes.)
> 
> The motivation here is that we would rather like to get rid of
> things like #ifdef __NetBSD__ in our sources (in favour of doing
> checks in configure for presence/absence of particular functions
> and acting accordingly), and also avoid using "uname" to figure
> out our compile target. That's very likely to break platforms
> we can't test on, so the idea is to identify which platforms
> people do care about, and make sure we are testing them, and
> then not worry about breaking anything that we aren't testing.
> 
> Also I think it doesn't do our users any favours to claim to
> support platform Foo if in fact it doesn't even compile.
> 

I can only speak for pkgsrc, qemu/Illumos (SmartOS) is actively maintained.

I have got an access to an Illumos machine for pkgsrc developers. Once I
will sort out NetBSD issues I will test qemu over there. I cannot speak
for Oracle Solaris and other proprietary Operating Systems.

I should get shell account for myself for DragonFly and Minix within 2
months.

I cannot maintain non-NetBSD targets beyond occasional and trivial
patches thought.

I will keep upstreaming small chunks of patches for NetBSD and let's see
how it will go. Thanks for help!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-04-25 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 23:27 [Qemu-devel] NetBSD maintenance Kamil Rytarowski
2017-04-23 10:19 ` Peter Maydell
2017-04-23 22:45   ` Kamil Rytarowski
2017-04-24  7:26     ` Fam Zheng
2017-04-24  7:54       ` Kamil Rytarowski
2017-04-24 10:12     ` Peter Maydell
2017-04-25 13:49       ` Kamil Rytarowski [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=7eea43e9-08d1-256c-a15b-d5b135a0725f@gmx.com \
    --to=n54@gmx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).