On 28/03/2019 16:25, Douglas R. Reno via blfs-dev wrote:
On 3/28/19 2:28 AM, Pierre Labastie via blfs-dev wrote:
On 28/03/2019 03:59, Bruce Dubbs via blfs-dev wrote:
There are just too many problems with meson-0.50.0. Therefore I
have reverted
to meson-0.49.2 in lfs-svn until it gets fixed.
If this is a conclusion of private discussions, please make them
public, or
summarize them... If it is not, well, what are the problems you see?
I do not
see evidence for problems on the mailing lists...
Pierre
The new version of Meson broke 50% of GNOME packages. They removed
some functions without deprecating them, removed some deprecated
options without documenting them, completely changed the output of the
JSON interpreter (breaking Tracker and making it impossible to compile
otherwise) (and did so undocumented), and changed =false to =disabled
(see Ken's message regarding glib-2.60.0).
All of these changes were done upstream without communication to
downstreams, either on mailing lists or in their release notes. In
addition, there are well over 1,000 issues on GitHub.
I stand by my opinion that this version of Meson should've been
Meson-1.0.0...
Thanks for the answer, Douglas, I understand better. Don't we need to
change back some "disabled" to "false" in some BLFS packages, now? grepping:
----
networking/netlibs/glib-networking.xml: -Dlibproxy=disabled ..
&&
general/genlib/glib2.xml: -Dselinux=disabled \
----
I agree that moving to meson while they are still in a development
process may be premature. But I like the idea:
- autotools are awful to use. Somebody (I think Ken) told that he
couldn't understand configure.ac. The use of m4+bash really makes
developers' life hard...
- Cmake look like they are reinventing the wheel (new language, with
hard to find doc, complicated layout: it took me several hours to
understand why some #define HAVE_X11 changed from "1" to "TRUE" between
cmake 3.13.4 and cmake 3.14). Note that this behavior was not specified
in the docs, so that the fault was rather to the KDE folks, who used an
undocumented feature, rather than using the recommended setting (they
have fixed that now).
- meson uses a well established and documented language (Python). It has
an easy (once you have found it in the doc) way to enumerate options
with their defaults (mkdir build; cd build; meson setup; meson
configure. I agree it is not immediate). But the output is clear.
Compare with the output of ./configure --help, where you never know,
when you see a help on --disable/--enable, whether the default is
disabled or enabled. You usually have to read configure or configure .ac
to see what is the default.
But meson is still in development according to [1]. Major version zero
means "Anything may change at any time. The public API should not be
considered stable." It looks like they are far from the 1.0.0 release :)
Pierre
[1] https://semver.org/
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
