install doesn't set path components permissions with -m like coreutils version
Open
Nobody has claimed this yet.
U - install
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
GNU coreutils behavior:
$ install -m 755 -d ./path/to/dir
$ stat -c %a path
755
$ stat -c %a path/to
755
$ stat -c %a path/to/dir
755
uutils --version 0.2.2 behavior:
$ install -m 755 -d ./path/to/dir
$ stat -c %a path
775
$ stat -c %a path/to
775
$ stat -c %a path/to/dir
755
Only the last component of the path receives the desired permissions. Is this intentional?
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 reproducing the install -m 755 -d behavior shown in the issue and compare permissions for each path component with GNU coreutils. Trace the install command's directory-creation handling. Done means every newly created component receives the requested mode, with a regression check covering the nested path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100