Yes that's ok with me too! I think for my usage my main entry point is standalone, but I know some users interact with it through GUI frontends like https://apps.gnome.org/MetadataCleaner/ and https://0xacab.org/jfriedli/mat2-quasar-frontend
But perhaps for consistency with other systems https://0xacab.org/jvoisin/mat2/-/blob/master/INSTALL.md, renaming it to mat2 would be best. Only FreeBSD has py-mat2, I believe. On Thu, 2024-07-18 at 16:29 +0200, Omar Polo wrote: > On 2024/07/18 13:04:40 +0100, Stuart Henderson <s...@spacehopper.org> > wrote: > > On 2024/07/18 13:00, Omar Polo wrote: > > > On 2024/07/17 09:51:49 -0400, Jag Talon > > > <jag@aangat.lahat.computer> wrote: > > > > Ping! Does this look ok to everyone? > > > > > > with RUN_DEPENDS sorted and a tiny formatting change to DESCR > > > it's OK > > > op@ to import. > > > > > > Just a curiosity, why don't call it mat2 instead of py3-mat2? I > > > understand that it also provides a library, but I guess the main > > > entrypoint is the binary bin/mat2 and so the package could be > > > called > > > like that? > > > > If the main use is standalone, then that probably makes sense. > > > > > DISTNAME = mat2-${MODPY_EGG_VERSION} > > > -PKGNAME = py-${DISTNAME} > > > > > > CATEGORIES = multimedia > > > > > > @@ -20,14 +19,14 @@ > > > FLAVORS = python3 > > > FLAVOR = python3 > > > > If it doesn't have a py- prefix then please don't use > > FLAVOR=python3 > > of course, sorry for missing it. Here's a new tarball with the > packaged > called "mat2" and without FLAVORS. If it's really used as a library > too > (honsetly I haven't checked) then I'm also fine with readding the > prefix > and FLAVORS. > > (it's obviously ok op@ to import with or without the FLAVOR/py- > prefix) >
