I have attempted to make the transition from the old Makefile to meson for the slackbuilds.org and while I was ultimately successful I have several gripes.
I can not use --prefix=/usr --bindir=/bin, meson forces me to set --prefix=/ --bindir=bin and then add explicit relative paths for everything else. For example --mandir=usr/man. This is an intentional misfeature in meson, please see. https://github.com/mesonbuild/meson/issues/2561
--datadir is not --docdir, but since loksh does not install any actual data I was able to get away with --datadir=usr and then after install mv -- $PKG/usr/doc/$PRGNAM $PKG/usr/doc/$PRGNAM-$VERSION.
It was possible to override the binary name with BIN_NAME using the Makefile, now with meson I have to use mv(1). This is required to not conflict with ksh (Even though at&t killed that project...).
I have attempted to make the transition from the old Makefile to meson for the slackbuilds.org and while I was ultimately successful I have several gripes.
--prefix=/usr --bindir=/bin, meson forces me to set--prefix=/ --bindir=binand then add explicit relative paths for everything else. For example--mandir=usr/man. This is an intentional misfeature in meson, please see. https://github.com/mesonbuild/meson/issues/2561--datadiris not--docdir, but since loksh does not install any actual data I was able to get away with--datadir=usrand then after installmv -- $PKG/usr/doc/$PRGNAM $PKG/usr/doc/$PRGNAM-$VERSION.BIN_NAMEusing the Makefile, now with meson I have to usemv(1). This is required to not conflict with ksh (Even though at&t killed that project...).