Hello,
However(!), datediff is already an existing tool in community/dateutils, which seems to have a similar use case as your tool does.
Well then the executable needs to be renamed, or conflicts must be added to the PKGBUILD to conflict community/dateutils
Adding the extension to the executable is non-standard, lots of binaries are plaintext, but they do not carry their extension. Imagine you rewrite your tool to use python instead, now you and everyone else who relies on the tool has to deal with the breaking change, whereas if the extension is never present, this isn't a problem.
Not always, sometimes if it is contained in the name it is fine, for example acme.sh keeps its extension because its within the actual name of the software. It would also be a good way to differentiate and prevent conflict between community/dateutils and this package.
md5 is broken and should not be used, sha256 or similar would be advised.
I do not see md5 being used within any repositories anymore, most use SHA256SUM, but some use SHA512SUM, whatever floats your bloat. -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev