Hello,
Indeed Hroptatyr's 'C-code datediff' already exists in community as 'dateutils'. It is not desirable to install the datediff.sh script as 'datediff' to avoid such instance of conflict.. However, what binary name would be cool to install the script with?
Well personally I would just keep the .sh, keep it simple and prevents confusion.
C-code datediff only accepts ISO-8601 dates, whereas the datediff.sh script warps `GNU date', if available (which usually is) to process input dates to ISO-8601 before calendrical calculations are performed, and it is verbose by defaults so you get a lot of info about any two dates instantly after typing them.
Well, if it is a replacement, add "conflicts=('dateutil')" to your PKGBUILD, this will mean you will not be able to have dateutil and your package installed on the same system, but it will prevent the conflict of file names.
Will use other checksum algos... Will switch to sha1. Thanks!
I list the most common two, and you pick the least common sha xD -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev