Let utilities identify themselves as being part of uutils in `--help` and `--version`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
Start by locating the implementations of the find and xargs --help and --version entry points, then check the corresponding output for the other utilities covered by this repository. Update the identification text consistently so help mentions that the utility is part of uutils and version output names uutils, including replacing find's Rust label; done when the outputs clearly identify their origin.
Written by the indexing model from the issue text.
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, find --version prints find (Rust) 0.8.. Instead of Rust I suggest using uutils. Note that xargs does not print any affiliation.
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
- Dominant language
- Rust
- Stars
- 649
- Forks
- 101
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 11
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.
More from uutils/findutils
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
good first issue
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
good first issue
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in uutils/findutils
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100