On Wed, 12 Mar 2025, Duncan Roe wrote:
I agree it would be poor use of your time. Anyone who cares can browse https://repology.org/repository/slackbuilds/problems for their email. That's what I do.
Yah, repology.org is very useful. I highly recommend it for any SlackBuild maintainer. That said... some of the stuff I package, doesn't exist in any other distro. In that case, repology can't help: it doesn't actually track the upstream project, only distro repos. If none of those repos have my package, there's nothing for it to compare to. Example: https://repology.org//projects/?search=hatari-tos-roms ...that one's not a great example: it's a repackaging of ROM images from the 1980s. It'll never need a version update (though it might need the homepage and download URLs updated some day). Better example: https://repology.org//projects/?search=cicb The other subtle thing about using repology to track updates... you're always a bit behind. repology won't notice that project XYZwhatever has updated, it'll only notice when some distro repo has updated their build/package of it. _______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
