Search Criteria
Package Details: porkbun-dynamic-dns-python-git r17.716794b-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/porkbun-dynamic-dns-python-git.git (read-only, click to copy) |
|---|---|
| Package Base: | porkbun-dynamic-dns-python-git |
| Description: | A fork of the official Porkbun dynamic DNS client written in Python |
| Upstream URL: | https://git.exozy.me/exozyme/porkbun-dynamic-dns-python |
| Keywords: | ddns dns domain dynamic porkbun python |
| Licenses: | MIT |
| Submitter: | dodecahedron |
| Maintainer: | dodecahedron |
| Last Packager: | dodecahedron |
| Votes: | 2 |
| Popularity: | 0.000004 |
| First Submitted: | 2022-05-20 16:06 (UTC) |
| Last Updated: | 2022-07-21 19:02 (UTC) |
Dependencies (2)
- python (python32AUR, python37AUR, python310AUR)
- python-requests
Latest Comments
txtsd commented on 2022-07-28 17:14 (UTC)
scoffs
Your fork is definitely better with the systemd timer and everything. It needs its own name at this point though. Treat yo'self. You deserve it.
Call it porkbun-ddns, that's different enough while retaining the meaning.
dodecahedron commented on 2022-07-28 16:32 (UTC)
Well yes, I wasn't aiming for 100% compatibility especially for configuration options that I didn't agree with (for instance, the vast majority of people won't customize the endpoint. Even if you did reuse your config from the official version with an endpoint key, it wouldn't do anything.) Also, the fork doesn't take any command line arguments since it's meant to be used with the systemd timer.
The whole reason this fork exists is because the official version wants to be Python 2 compatible for some bizarre reason preventing it from being modernized and cleaned up.
txtsd commented on 2022-07-28 15:26 (UTC)
It isn't a drop-in replacement. The default configs are different. Upstream expects an endpoint key, while your fork expects a domain key.
The code /is/ cleaner though.
dodecahedron commented on 2022-07-28 15:16 (UTC)
This package uses the fork since it's a completely rewritten drop-in replacement for the official DDNS client, with much cleaner code and more features. I don't see anything wrong with the package name, since I doubt anyone would want to use the official client over the fork, and the package description mentions that a fork.
txtsd commented on 2022-07-28 14:01 (UTC)
Why is upstream a fork instead of the official repo?
The package name should reflect that it's a fork.