Details
Please add a busybox style --install option when running the "coreutils" binary as shipped in the releases. Including supporting --install -s <folder>
This is a nice to have feature which creates either hard-links or soft-links for each of the functions in the defined folder. With all of the links pointing to the real path of the binary which ran the command.
Reasoning
Right now I can download a release. However, per the readme, if I want more than have a single binary, I need to install the entire build system.
- I would like to be able to set up a system with the coreutils binary as simply as I do with busybox.
- Releases do not include an install script or easy method to run coreutils functions other than
coreutils <function>.
coreutils -h and "README.md" included in releases never states that re-naming or linking the binary will cause it to behave as the named function.
- The closest it comes is mentioning it can be built as "a multicall (BusyBox-type) binary"
PS: I apologize if this has been requested before. GitHub seems to auto-strip quotes when searching for "--install"!
Details
Please add a busybox style
--installoption when running the "coreutils" binary as shipped in the releases. Including supporting--install -s <folder>This is a nice to have feature which creates either hard-links or soft-links for each of the functions in the defined folder. With all of the links pointing to the real path of the binary which ran the command.
Reasoning
Right now I can download a release. However, per the readme, if I want more than have a single binary, I need to install the entire build system.
coreutils <function>.coreutils -hand "README.md" included in releases never states that re-naming or linking the binary will cause it to behave as the named function.PS: I apologize if this has been requested before. GitHub seems to auto-strip quotes when searching for "--install"!