Hi,
On 20.12.2018 4.40, Stuart Young wrote:
Could this be reduced this from an error to a warning, with the
command-line option suppressing the warning?
Perhaps as well as producing the warning, the build could sleep for say
30 seconds after producing the warning message. This would be noticeable
if you're building it yourself (which would definitely get the message
out there), but wouldn't stop automated build processes (as it's not
stopping, just sleeping).
At a later date (when meson has more exposure) then perhaps we could
move from a warning to an error.
Thoughts?
So it would take 2 releases i.e. about 1/2 year?
* In next release autotools build is going to warn that meson should be
used instead, as autotools support will be eventually removed.
* Next release from that:
- errors out if specific option isn't used for doing building with
autotools
- tells that autotools support will be removed in following release
* Release after that removes autotools support.
(I assume Emil would be the person supporting Autotools during this as
he had already volunteered for it.)
While I think above is closer to how other large projects do deprecation
in general (= have clear deprecation period/releases), build system
changes are probably more often done just with flag day (early in the
release cycle, as maintaining multiple build systems can be pretty large
pain).
- Eero
On Thu, 20 Dec 2018 at 07:37, Gert Wollny <gw.foss...@gmail.com
<mailto:gw.foss...@gmail.com>> wrote:
Am Mittwoch, den 19.12.2018, 12:19 -0500 schrieb Ilia Mirkin:
> On Sun, Dec 16, 2018 at 6:24 AM Gert Wollny <gw.foss...@gmail.com
<mailto:gw.foss...@gmail.com>>
> wrote:
> >
> > 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
> >
> > Signed-off-by: Gert Wollny <gw.foss...@gmail.com
<mailto:gw.foss...@gmail.com>>
>
> In case it's not clear from the later discussion:
>
> Strongly NAKed-by: Ilia Mirkin <imir...@alum.mit.edu
<mailto:imir...@alum.mit.edu>>
> This should not be applied to the repository.
You should probably add this to the patch proposals that want to remove
autotools then.
I'm certainly not going to push this patch with your NAK, but I'd like
to ask you to reconsider: All this patch does is require to add --
enable-autotools to the configure call once - a little hickup in the
workflow of those who do not yet use exclusively meson, but it gets the
message out to the others that things are going to change.
Best,
Gert
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org <mailto:mesa-dev@lists.freedesktop.org>
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
--
Stuart Young (aka Cefiar)
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
