Let utilities identify themselves as being part of uutils in `--help` and `--version`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
I had a tool in $PATH and needed to determine whether its from GNU coreutils/findutils/... , busybox, or uutils. While the GNU and Busybox state their origin in the --help and --version , uutils stays (mostly) silent about its origin.
Add something like part of uutils to --help and also mention uutils in the --version output.
Currently, uutils-coreutils only implements the indicator in the --version output.
Note: This bug is part of a series of bugreports across all tools of uutils. Please check wether I've covered all your utilities.
Related:
- https://github.com/uutils/coreutils/issues/7427
- https://github.com/uutils/coreutils/issues/12114
- https://github.com/uutils/tar/issues/273
- https://github.com/uutils/procps/issues/690
- https://github.com/uutils/util-linux/issues/538
- https://github.com/uutils/acl/issues/298
- https://github.com/uutils/findutils/issues/672
- https://github.com/uutils/sed/issues/407
- https://github.com/uutils/awk/issues/2
- https://github.com/uutils/diffutils/issues/222
- https://github.com/uutils/bsdutils/issues/128
- https://github.com/uutils/shadow-rs/issues/161
- https://github.com/uutils/hostname/issues/290
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing uutils-coreutils implementation that adds the uutils indicator to --version, then review each utility's --help and --version output. Check the related utility issues to identify coverage expectations, and verify that every coreutils utility identifies itself in both outputs without breaking existing formatting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100