Sorry. Copy-paste decided to send a msg rather than paste into it. On Fri, 21 Dec 2018 at 17:36, Stuart Young <cef...@gmail.com> wrote:
> On Fri, 21 Dec 2018 at 04:18, Eero Tamminen <eero.t.tammi...@intel.com> > wrote: > >> 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? >> > > Not necessarily. IMO if there's enough consensus between 19.0 and 19.1, > then changing it to an error could happen then. I'm basing this on the fact > that every .0 release specifically says something like this: > Mesa 18.3.0 is a new development release. People who are concerned with stability and reliability should stick with a previous release or wait for Mesa 18.3.1. Of course, this isn't my call. I'm just trying to suggest ways to break the deadlock. * 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). >> > > Yes, but at the moment we have no consensus and a deadlock on the issue. > -- Stuart Young (aka Cefiar)
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev