termux / repology-metadata Goto Github PK

For autossh for example we have TERMUX_PKG_DEPENDS="openssh | dropbear". In the generated packages.json we get

    "name": "autossh",
    "version": "1.4g",
    "description": "Automatically restart SSH sessions and tunnels",
    "homepage": "https://www.harding.motd.ca/autossh/",
    "depends": [
      "openssh",
      "|",
      "dropbear"
    ],

We can change the script to always use the first package in the "or" statement (alternatively we could make have "depends" : [ "openssh | dropbear" ], but I guess repology doesn't handle that at the moment)

Subpackages are currently missing completely in our data dump.

Not sure if there is a reason for this? I guess script authors (myself included) forgot about them, or were just to lazy to parse them..

Currently we can explore the possibility of adding the following fields to our generated JSON data:-

From termux/termux-packages@b760237#commitcomment-66181066

• package source
• package recipe
• package raw recipe
• package patches
• package raw patches
• (Add more?)

As seen if for example the latest update. Probably need to strip away the version.

What can be done:

• properties.sh can be sourced from the termux-packages repository itself
• jq can be used by generate-repology-metadata.sh to get the list of repositories from 'repos.json' instead of passing hard-coded list of paths

Note that this is just a tracking issue and I've already started work on this

This caused Repology to recently stop picking up updates from our repos. The reason was due to a unallowed character in JSON string " (the double quotes). It would be great if we can somehow patch our scripts to make sure the JSON is always valid, so that we don't end up in such situation again.

Link to the commit that fixed this:- termux/termux-packages@b760237