Re: For projects switching to Meson *only*

[Michael Catanzaro <mike catanzaro gmail com>]

On Thu, Apr 27, 2017 at 4:11 AM, Iain Lane <iain orangesquash org uk> 
wrote:
> As it happens I interacted with this script (in gnome-software)
> yesterday. I hadn't got a new enough jhbuild - the one I had was 
> trying
> to call ./configure instead of meson directly.
>
> The script AFAICS ignores unknown arguments. In particular, I was
> interested in passing some --enable/--disable flags to select features
> but I didn't find out how to do that short of explicitly extending it
> with those particular options. If you expect distributors to be using
> this, or if this is interesting for users of the build API, is having
> some support for ./configure <-> meson_options integration a 
> reasonable
> request?
>
> Otherwise, and this is what happens now that I upgraded jhbuild, using
> meson directly works fine. But if a goal of this is to smooth the
> transition path and avoid a requirement for tooling to be updated, 
> maybe
> it would be useful.

This compatibility issue seems like a very good argument for shipping 
the "compatibility" script in Continuous patches rather than 
application repositories.

Michael