On 2020/01/05 09:56, Heppler, J. Scott wrote: > of flavors > Reply-To: Organization: > > jgmenu has a new release with a major feature bump - it's own C-coded > menu generator that relegates python3+pmenu and lx+menu-cache to > options. The new "apps" modules will also reference xfce4 garcon menus. > > Since version 2.1 a third build option will generate an xfce4-panel menu > plugin. > > For more details, see > https://github.com/johanmalm/jgmenu/blob/master/docs/relnotes/4.0.txt > > From the porters's handbook > "You won't care about some options. It makes no sense to disable some > stuff if it always works, and if the dependencies are quite small." > > My questions revolve around "small" and how to to provide for community > testing. I suspect cwm users would be very interested in a jgmenu-apps > flavor and if it tests well in cwm and other lightweight WM's drop the > python3, menu-cache, libfm dependencies. pmenu always works, is slower > and python3 is not "quite small" although python2 will loose support > later this year and python3 tends to get installed by other ports. > menu-cache, libfm and gnome/mate-menus are smaller and have always > worked and may be helpful to porters who run lightweight desktops but > need to test ports with freedesktop *.desktop entries. > > I'm leaning towards 2 flavors initially: > jgmenu-apps > and > jgmenu-lx. > > Comments? Suggestions? > > -- > J. Scott Heppler >
These are all separate programs aren't they? That would indicate using "multi-packages" - enabling everything in the port build, but split the various executables into separate packages which can each have their own dependencies. See FLAVORS AND MULTI_PACKAGES in bsd.port.mk(5) and see x11/xkbset for the simplest example I could find of a port using this.
