Tsss.... come on, too little sleep anyone?
(me sure, LOL!)
All suggested possibilities are valid and useful.
And that rodocop called the Groups2 macro
an "extension" ist just because everything that "extends" the out-of-box KM-functions is an "extension". XPI-addons and kmm-macros and everything. We're just often tossing everything into the same pot wordwise.
My tip is, before installing anything to look inside a 7z which files it really contains.
Just don't be confused by that "kmextensions" folder. Actually this one has zero function for the browser itself!
It does not contain any code. It's just a common place to collect tiny text (ini) files with a 1-line description and a 7z-file-list, if an author decides to add this. Purely optional, and purely as convenience for (especially non-expert) users. So, just the existence of this ini-file in a 7z says nothing about the type of extension (10-line macro? giant FF-addon?)
The one thing which actually needs those ini-files, is yet another extension: The "Extensions Manager
". Which is -you guessed it- purely optional too ;-) It just makes handling and overview a bit easier. Provided the macro author has added such a little ini-file of course.
But the installation process itself in KM, of nearly all macros/extensions, is to simply drop their files into the matching folders and restart the brower. And Un-Installation is to remove those files again out of those folders, for example using the Windows file explorer. No "Manager" really needed.
Just remember to manually delete the "startupCache
" in your Profile folder after changes, when using modern KM7X-versions and noticing any glitches. Especially the newest KM77-Goanna seems extremely touchy with that startupCache thing. (In old KM1.X version the equivalent are the 2 *.dat files in the components folder, but not for simple macros, only for complicated jar-extensions)