Quoting Ilia Mirkin (2019-01-11 14:43:26) > On Fri, Jan 11, 2019 at 5:38 PM Matt Turner <matts...@gmail.com> wrote: > > > > On Fri, Jan 11, 2019 at 2:28 PM Ilia Mirkin <imir...@alum.mit.edu> wrote: > > > > > > On Fri, Jan 11, 2019 at 5:12 PM Matt Turner <matts...@gmail.com> wrote: > > > > > > > > From: Gert Wollny <gw.foss...@gmail.com> > > > > > > > > Since Meson will eventually be the only build system deprecate autotools > > > > now. It can still be used by invoking configure with the flag > > > > --enable-autotools > > > > > > > > NAKed-by: Ilia Mirkin <imir...@alum.mit.edu> > > > > > > [nouveau] > > > > > > > Acked-by: Eric Engestrom <eric.engest...@intel.com> > > > > Acked-by: Kenneth Graunke <kenn...@whitecape.org> > > > > Acked-by: Lionel Landwerlin <lionel.g.landwer...@intel.com> > > > > Acked-by: Jason Ekstrand <ja...@jlekstrand.net> > > > > Reviewed-by: Matt Turner <matts...@gmail.com> > > > > > > [intel] > > > > > > > Acked-by: Rob Clark <robdcl...@gmail.com> > > > > > > [freedreno] > > > > > > > Acked-by: Marek Olšák <marek.ol...@amd.com> > > > > > > [radeon] > > > > > > > Reviewed-by: Christian Gmeiner <christian.gmei...@gmail.com> > > > > > > [etnaviv] > > > > > > > Reviewed-by: Eric Anholt <e...@anholt.net> > > > > > > [vc4] > > > > > > > Signed-off-by: Gert Wollny <gw.foss...@gmail.com> > > > > > > [sorry Gert, not sure how to classify you] > > > > > > I think the vmware team (which largely maintains llvmpipe and svga) is > > > probably worth hearing from -- I believe they've largely stayed out of > > > it. But an ack/nack would be good. Also virgl isn't represented, I > > > believe. Probably not *required* to hear from these, but perhaps worth > > > a poke? > > > > Sure. I've Cc'd Dave, Brian, José, and Roland on this reply. > > > > > > --- > > > > I think there's support for overriding the sole objection to this patch. > > > > > > > > To confirm: > > > > > > > > (1) The plan is to remove Autotools, perhaps after the 19.0 release > > > > > > > > (2) This patch's purpose is to ensure that everyone knows that > > > > Autotools will be going away (think: people who build Mesa as > > > > part of an automated process and wouldn't notice a deprecation > > > > warning unless it requires some action from them) > > > > > > If it's being removed _after_ the 19.0 release, does it make sense to > > > have a patch like this _in_ the 19.0 release? (Perhaps the answer is > > > `yes', but I'd still like to ask the question.) > > > > Yes, I think so -- I might be missing or misunderstanding a part of > > your question though. > > > > My thinking is in 19.0 mark autotools as deprecated with this patch so > > as to ensure everyone knows, and depending on progress on the blocking > > issues to aim for removal after the 19.0 branch point. > > Perhaps I was just responding (in my head) too literally to your > comment about automated processes. If the automated process is around > building HEAD, then it's not necessary for this change to be in the > release. But I guess you also want to catch the people with automated > processes against released versions who might have various > hypothetical issues with meson, and you want them to report the issues > while they still have an easy fallback to autotools, as opposed to > when there's no other option and they're stuck in an inconvenient > situation. > > So ... the answer is `yes'. > > -ilia
Yes. In particular we'd like to make sure that distros know that we're planning on changing the build system sometime after 19.0. Since many distro wrappers only show you the config log if something goes wrong, they're unlikely to notice a warning that autotools support is deprecated unless the build stops working. Dylan
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
