Closed GeoffreyFrogeye closed 8 years ago
Awesome, thanks for doing that!
To my ears, having a mail-sieve-verifier
command seems clunky. Maybe verify-sieve
or simply sieve
? If the command was simply sieve
, we'd need a subcommand verify
or some such. So the syntax would be something like:
sieve verify my.sieve
Alternatively, maybe it makes sense to rename the project to match the binary, i.e. check-sieve? That might make sense since the library is named libchecksieve
Yes, renaming the project is way better. Having a an executable with the same name that the project have is a very good thing so you don't even have to check the documentation to make it work, but yeah, mail-sieve-verifier
is too long. Also, it's not a big deal since the project is relatively small for now.
Okay, I've renamed the project and cut a new version, v0.3
Thanks!
Here's the always-up-to-date -git
package: https://aur4.archlinux.org/packages/check-sieve-git
And since you made a new version, here's the regular package https://aur4.archlinux.org/packages/check-sieve
(just posting it here, so I don't need to open a new issue)
I wanted to do a package on Arch User Repository, but I thought that installing
mail-sieve-verifier(-git)
and having acheck-sieve
command was kinda odd. Shall we change the name of the executable or leave like this?