From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:48558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h2ETN-0004Sv-6y for qemu-devel@nongnu.org; Fri, 08 Mar 2019 07:19:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h2ETJ-0000Ir-MG for qemu-devel@nongnu.org; Fri, 08 Mar 2019 07:19:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45710) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h2ETJ-0008UW-ED for qemu-devel@nongnu.org; Fri, 08 Mar 2019 07:19:29 -0500 Date: Fri, 8 Mar 2019 12:19:18 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20190308121918.GE19819@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <3246431b-8d6e-f2bc-e0f0-99d80384d97b@redhat.com> <87r2bigarf.fsf@zen.linaroharston> <62408d6c-5a61-ffb2-f810-6ef36703b277@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] converting build system to Meson? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: =?utf-8?Q?Marc-Andr=C3=A9?= Lureau , Paolo Bonzini , Thomas Huth , Alex =?utf-8?Q?Benn=C3=A9e?= , QEMU Developers , Richard Henderson On Thu, Mar 07, 2019 at 06:18:28PM +0000, Peter Maydell wrote: > On Thu, 7 Mar 2019 at 18:17, Marc-Andr=C3=A9 Lureau > wrote: > > As someone who has also been annoyed having to support in-tree and > > out-of-tree, I support that move. I used to be a pretty happy use of > > in-tree builds, but out-of-tree his generally equally convenient. > > > > Who is volunteering to do patches to deprecate the support? warning i= n > > 4.0, and error in 4.1? >=20 > Do we need to bother to deprecate it? It doesn't affect end-users, > only those who build QEMU, and the change is easy... Yeah, I don't think we need to deprecate it. If we get configure to report an error straightaway it will be obviuous to developers what they need to change to adapt. Sufficient to just announce on the mailing list that we intend todo it in the start of the next dev cycle. Gives developers plenty of time to adapt, and it will be in the release notes for the next release to alert downstream consumers. Regards, Daniel --=20 |: https://berrange.com -o- https://www.flickr.com/photos/dberran= ge :| |: https://libvirt.org -o- https://fstop138.berrange.c= om :| |: https://entangle-photo.org -o- https://www.instagram.com/dberran= ge :|