Re: [NEW] x11/jgmenu -> V2.0

On 2019/02/02 11:20, Brian Callahan wrote:
>
>
> On 2/2/19 10:27 AM, Heppler, J. Scott wrote:
> > Hi ports,
> >
> > Attached is a port that builds the latest release of jgmenu. Upstream
> > has made a large number of commits since 1.6.  Some of these commits
> > targeted OpenBSD issues.
> >
> > Menu generation using XDG and firefox bookmarks has been deactivated and
> > the gtar dependency removed.
> >
> > More details here:
> >
> > https://github.com/johanmalm/jgmenu/blob/master/docs/relnotes/2.0.txt
>
> Fixed up and tightened version attached.
> Additionally, portcheck -N says:
> Python module without compiled version, consider using ${MODPY_BIN}
> ${MODPY_LIBDIR}/compileall.py: lib/jgmenu/jgmenu-config.py
> Python module without compiled version, consider using ${MODPY_BIN}
> ${MODPY_LIBDIR}/compileall.py: lib/jgmenu/jgmenu-pmenu.py
> Python module without compiled version, consider using ${MODPY_BIN}
> ${MODPY_LIBDIR}/compileall.py: lib/jgmenu/jgmenu-unity-hack.py
>
> This may or may not be relevant to you.

Not required. pyc files are only used when a module is imported not
run directly.

> ~Brian
>

+This jgmenu build can generate an X11 application menu 3 different ways:

slightly nitpicking, but it doesn't feel quite right to me using number
3 in text followed by a numbered list, I think it would read better with
"s/3 different/three different/".

+ 1) lx using additional packages menu-cache and gnome(mate)-menus
+ 2) ob from an existing openbox menu.xml file
+ 3) pmenu with python3 text parsing

I would write "jgmenu-lx" or "jgmenu-lx(1)" instead of just "lx"
(and same for ob/pmenu).

Otherwise OK