On 2019/02/04 20:59, Klemens Nanni wrote:
> On Fri, Feb 01, 2019 at 10:30:06PM +0000, Stuart Henderson wrote:
> > OK sthen@ if someone would like to import ..
>
> $ doas make install
> [...]
> $ mmaker dwm
> env: python: No such file or directory
> $ cat `which mmaker`
> #!/usr/bin/env python
> import MenuMaker.CLI
That's weird. It's substituted correctly here via autoconf/Makefile -
what output do you get from "make configure"?
> $ ln -s `which python3` ~/bin/python
> $ mmaker dwm
> Traceback (most recent call last):
> File "/usr/local/bin/mmaker", line 2, in <module>
> import MenuMaker.CLI
> ModuleNotFoundError: No module named 'MenuMaker'
Works at runtime here too (though it doesn't have a "dwm" option ..)
> That seems off. I did not look into the missing module, but since we
> pin Python 3.x, the shebang should be fixed at least.
>
> Here's some nit-picking.
>
> --- Makefile Fri Feb 1 19:38:31 2019
> +++ Makefile.new Mon Feb 4 20:48:48 2019
> @@ -1,8 +1,8 @@
> # $OpenBSD:$
> -#
> +
> COMMENT = menu generation utility for X window managers
> -VERSION= 0.99.10
> -DISTNAME= menumaker-${VERSION}
> +VERSION = 0.99.10
> +DISTNAME = menumaker-${VERSION}
> CATEGORIES = x11
>
> MASTER_SITES = ${MASTER_SITE_SOURCEFORGE:=menumaker/}
>
Can just be CONFIGURE_STYLE=gnu as well (and VERSION rolled into DISTNAME).
(Not sure why I didn't pick up on it being weird with the no-autoheader before!)
