I'm looking at updating x11/yad and it now uses autoreconf -ivf && intltoolize.
https://github.com/v1cont/yad With this /usr/ports/x11/yad/Makefile # $OpenBSD: Makefile,v 1.19 2019/07/12 21:02:30 sthen Exp $ COMMENT= display graphical dialogs from shell scripts or command line GH_ACCOUNT= v1cont GH_PROJECT= yad GH_TAGNAME= v5.0 CATEGORIES= x11 HOMEPAGE= https://github.com/v1cont/yad # GPLv3 PERMIT_PACKAGE= Yes WANTLIB += atk-1.0 c cairo cairo-gobject gdk-3 gdk_pixbuf-2.0 WANTLIB += gio-2.0 glib-2.0 gobject-2.0 gtk-3 intl pango-1.0 pangocairo-1.0 WANTLIB += pthread fribidi MODULES= textproc/intltool USE_GMAKE= Yes LIB_DEPENDS= devel/gettext,-runtime \ x11/gtk+3 RUN_DEPENDS= x11/gtk HOMEPAGE= https://github.com/v1cont/yad # GPLv3 PERMIT_PACKAGE= Yes WANTLIB += atk-1.0 c cairo cairo-gobject gdk-3 gdk_pixbuf-2.0 WANTLIB += gio-2.0 glib-2.0 gobject-2.0 gtk-3 intl pango-1.0 pangocairo-1.0 WANTLIB += pthread fribidi MODULES= textproc/intltool USE_GMAKE= Yes LIB_DEPENDS= devel/gettext,-runtime \ x11/gtk+3 RUN_DEPENDS= x11/gtk+3,-guic CONFIGURE_STYLE= autoreconf libtoolize AUTOCONF_VERSION= 2.69 AUTOMAKE_VERSION= 1.14 USE_LIBTOOL= Yes CONFIGURE_ARGS= --with-gtk=gtk3 \ --disable-html \ --with-rgb=${X11BASE}/share/X11/rgb.txt CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \ LDFLAGS="-L${LOCALBASE}/lib" I get this make build error config.status: creating Makefile config.status: error: cannot find input file: `po/Makefile.in.in' *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2851 'do-configure') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2871 '/usr/ports/pobj/yad-5.0/.configure_done') *** Error 1 in /usr/ports/x11/yad (/usr/ports/infrastructure/mk/bsd.port.mk:2556 'build') autoreconf does generate a ~/pobj/yad-5.0/po/Makefile.in but no ~po/Makefile.in.in Am I implementing autoreconf -ivf && intltoolize correctly? Is there a cleaner way to do this? The code also runs glib-compile-schemas which I plan to disable and @tag in PLIST. Last question. Present code can use webkitgtk2-4.0 which has had some security updates. I was planning on continuing --disable-html unless convinced otherwise. Thanks -- J. Scott Heppler
