From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dylan Baker Subject: Re: [RFC libdrm 0/2] Replace the build system with meson Date: Wed, 22 Mar 2017 14:05:56 -0700 Message-ID: <149021675652.24719.2607609417568258504@localhost.localdomain> References: <87mvceadug.fsf@intel.com> <149011337067.7993.8735883601342413966@localhost.localdomain> <87fui5afd8.fsf@intel.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1362802354==" Return-path: In-Reply-To: <87fui5afd8.fsf@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Jani Nikula , dri-devel@lists.freedesktop.org Cc: mesa-dev@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1362802354== Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="===============0354705181247736618==" Content-Disposition: inline --===============0354705181247736618== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Quoting Jani Nikula (2017-03-22 01:24:19) > On Tue, 21 Mar 2017, Dylan Baker wrote: > > Quoting Jani Nikula (2017-03-21 07:44:55) > >> How does meson handle build file backwards compatibility between meson > >> versions? I don't intend to flame, but I've found for some reason many > >> python projects don't seem to take this very seriously. Either having > >> conditionals in build files to support building with several meson > >> versions or always requiring the latest and greatest version would be > >> rather annoying. > > > > Meson makes backwards compatible changes, and the version can be > > queried using `meson.version()`, which works using meson's version > > comparison mechanism. I would say this about meson, it's not a 'python > > project', it's 'a project written in python', > = > This is what I meant above, although I clearly didn't write it that way. I don't think I was exactly clear in what I said either, I would describe S= Cons as a "python project", and meson as a "project written in python", since SC= ons is python and has some of the warts that make backwards compatibility in py= thon projects hard (changes that work in the majority case break in some niche u= se cases), where meson has a parser/generator written in python. > > and they've taken great pains to not expose python in meson, and > > reserve the right to reimplement in a different language if python > > becomes an issue. > = > Right. That helps avoid many of the issues e.g. Sphinx has with the > configuration files being pure python. Yes, sphinx's configuration files are awful for just that reason. Dylan --===============0354705181247736618== MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Description: signature Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEUwPMqo/+5aFHLzU4CJ4WlhQGiO8FAljS5zQACgkQCJ4WlhQG iO8ZpAf/WbCKhCm9hn4oSZGySDAq+HlkrPBlpIImJms2rjQ8KkaM0VuSFG/Nm2u8 7OmgPubwCe8mmBVcr2uK49dTQAT/IO3xCipHwylNQZa93Ojk78AqWgxVdnc7SQyc GXhUhkWc1cMqTOQxuX9QapxkfkJkoQyew0p6W3I82e5ADxYsl6iHAVCZuuxYRW2l FAMY/yPFq4T/7C9lS6n7zB9j2PPJu7fK4z0ItOhX/i+R2M6U0BJInjxku/We7ELa Fj05gak3boSc2tTVnYbTCi7qlZ5Of+6B/eKjNPRZIlc9Fq9O7UXlYnIjVwhmOd5T mjuPCrYMrETxWeQi16VxyMRB/qQGQw== =y+sD -----END PGP SIGNATURE----- --===============0354705181247736618==-- --===============1362802354== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1362802354==--