@Nick-Hall the link above goes to a GitHub releases page for the experimental WebSearch addon by @Urchello
The GitHub Releases appears to have some benefit for developers in maintaining a archive of releases. But it has a penalty in managing installed addon versions compared to the make.py/addons-__.json system of the Addon Manager.
Is that trade-off real? Or can a developer be more efficient (in both delivery and archiving) if they use the make.py approach?
You just improved the PO portion generation options of the addons-source make.py script. (Thank you!) The Usages section in the README.md in addons-source discusses using make.py directly from GitHub for a clone of addons-source repository.
Is there a simplified guide to leveraging the make.py (locally for an installed addon; or, on directly GitHub for a personal repository) for generating the PO and the listings/download folders? Specifically calling the make.py from within Gramps using Python Eval built-in, or Python Shell, SuperTool, gram.py addon gramplets