You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a man-page and TexInfo.
I wish that when installing yq it also setup a proper man-page and optionally a TexInfo documentation, so its usage and short documentation can be read offline with the most common standard Unix/Linux command man.
With pandoc or similar tools into your CI chain
You could automatically transcribe a Markdown documentation into a man-page.
Then have the man page deployed and setup with packaged distributions of yq.
This is a neat idea - I've got the man generation just about done, which makes a yq.1 man page file.
Any ideas as to how to distribute this? I'm thinking I'd just gzip as a separate release file..
Yes, I think that makes sense. I would both offer the yq.1.gz file as a separate file and include it along with the binaries in the .tar.gz archives. You should also instruct users to copy the file to /usr/local/share/man/man1 (software that is not managed by the package manager should be copied to /usr/local as opposed to /usr).
Add a man-page and TexInfo.
I wish that when installing
yq
it also setup a proper man-page and optionally a TexInfo documentation, so its usage and short documentation can be read offline with the most common standard Unix/Linux commandman
.With
pandoc
or similar tools into your CI chainYou could automatically transcribe a Markdown documentation into a man-page.
Then have the man page deployed and setup with packaged distributions of
yq
.Example with
README.md
Automatically create a man page. The README is not the best choice but I cite it as an example:
yq.1.txt
The text was updated successfully, but these errors were encountered: