Catalog of libraries?

[amtlib-dot-dll]

Usually a list of package names are provided in the wikis of many software (here, here and here), but the recipes require source tarballs like (from here)

{
    "name": "boost",
    "buildsystem": "simple",
    "build-commands": [
        "./bootstrap.sh --prefix=/app --with-libraries=date_time,filesystem,locale,regex,system,thread",
        "./b2 --build-type=minimal link=shared",
        "./b2 --build-type=minimal link=shared install"
    ],
    "sources": [
        {
            "type": "archive",
            "url": "https://downloads.sourceforge.net/project/boost/boost/1.60.0/boost_1_60_0.tar.bz2",
            "sha256": "686affff989ac2488f79a97b9479efb9f2abae035b5ed4d8226de6857933fd3b"
        }
    ],
    "cleanup": [
        "/include"
    ]
}

Finding the URLs of tens of source tarballs, and translate those wiki guides to build commands, are not easy, and recipe authors are wasting time doing the same thing again and again to collect those JSON clips. It would be absolutely better if a central catalog or wiki is provided for common libraries.

[TingPing]

They can just search for code from https://github.com/flathub

I don't think making a list of every possible module that ever exists is productive or worth-while.

[amtlib-dot-dll]

A wiki page should be a good idea

[hadess]

I use https://github.com/search?type=Code&q=org%3Aflathub+search_term, to look for inspiration. If there's more than a couple of users, we can probably get those added to the shared-modules git submodule.

[christian-rauch]

Why not just use homebrew https://docs.brew.sh/Homebrew-on-Linux as the catalogue?

Copy & pasting code snippets you found on the internet is not a very stable approach to maintaining software...

[louib]

I think that's what the shared modules are for, but unfortunately it's far from being an exhaustive catalog.