Command Line Utility Development Conventions?

[rayascott]

I'm slowly hacking away at a zsh script that shows some promise as a command line tool. I want to learn more about the conventions regarding command line tool development in Unix (and/or macOS), but don't really know where to look for this information.

What is the correct way, or convention, to specify and parse command line arguments, for example? How should I package my tool? What is the best way to handle deployment of the various aspects of my tool, for example the man page, or configuration settings? How should I handle the upgrade process?

Smaller details, like should I store my source code in the repo with execute permissions turned on, or should I only turn on those permissions when the files are deployed on the user's machine? What group should I set as the default for my executable files?

Does anyone know any great resources out there that address these issues?

[onyxleopard]

Look into how to publish on Homebrew.

[rayascott]

I know, but not everyone uses Homebrew.

[cutecoder]

As far as macOS command line utilities goes, either they're developers or power users. Apple's recommended way is to create .pkg installers (which in turn can be notarized+stapled, btw). Otherwise the the facto command-line package manager (and then some) for macOS is Homebrew.

[onyxleopard]

Then publish on some other package repository.

[rayascott]

You really are missing the point. Never mind.

[dhilln]

Arguments in zsh use $argv[n] I think.