[Mesa-dev] [PATCH mesa] drop autotools

[Andres Gomez]

On Mon, 2018-12-17 at 19:51 +0100, Bas Nieuwenhuizen wrote:
> On Mon, Dec 17, 2018 at 6:33 PM Juan A. Suarez Romero
> <jasuarez at igalia.com> wrote:
> > 
> > On Mon, 2018-12-03 at 10:21 +0000, Eric Engestrom wrote:
> > > Cc: Emil Velikov <emil.l.velikov at gmail.com>
> > > Cc: Andres Gomez <agomez at igalia.com>
> > > Cc: Juan A. Suarez Romero <jasuarez at igalia.com>
> > > Cc: Dylan Baker <dylan at pnwbakers.com>
> > > Signed-off-by: Eric Engestrom <eric.engestrom at intel.com>
> > > ---
> > > This patch depends on the releasing procedure in docs/releasing.html to
> > > be updated to not rely on autotools anymore.
> > > 
> > > I think our release managers (cc'ed) should work together and figure out
> > > the procedure they want to go by; only once that's done can we delete
> > > these 200+ files and 14k+ lines :)
> > 
> > 
> > I'll let others to talk. But my preference would be to land this for next 19.0
> > branchpoint, just a couple of days before the branchpoint, so 19.0.x releases
> > get rid of autotools.
> > 
> > This way we have time to fix any remaining issue, and make like easier for those
> > in charge of 18.3.x releases, which I think should support autotools until the
> > end of its life.
> 
> Can I suggest the inverse, pushing this long before any branchpoint?
> 
> As with any migration, users only start using when you force them too,
> and that means a bunch of non-working usecases are going to be
> detected once this patch is pushed and some more people are forced to
> it. Sure, the last call discussion served to tease some of these out,
> but I expect even more will turn up if you submit this.
> 
> Doing this far before the branchpoint gives more time to fix them.

FWIW, I agree with Bas here. Better to push this long before any
branchpoint.

I don't foresee many (if any) backports would be needed during a stable
cycle because of problems in the removed autotools files and, if fixes
are needed for meson, they are welcome.

-- 
Br,

Andres