How to use it?>

[lucasjinreal]

I installed it, and it's a single coreutils binary.......

i have to cp for coreutils cp???? this is insane, why need each simple command for a gaint big binary every single time..

[oech3]

You can manually symlink relatively or hardlink coreutils to cp. But .zip on GitHub's release page can't include symlinks or hardlinks because zip does not support them.

Also publishing indivisual binaries are discussed #5691 . But it is difficult too since it is 100 MB+.

[lucasjinreal]

But i think for cargo install it its ok, to organize each binary to uutils/xx folder, and if users (like) want all coreutils in rust replace offcial one, just export cargo/bin/coreutils/ to bashrc.

[oech3]

No. cargo install itself does not have a feature to make symlinks. It it one of a reason why this project cannot drop GNU make...

[lucasjinreal]

i mean, just using multiple binarys in Cargo.tml, and set path, why must using symlinks....

[oech3]

#9563 (comment)
So you want install copies of large coreutils binaries by default?

[oech3]

Please use make install MULTICALL=y. It is maximal effort we can unfortunately (or open a issue on cargo's repo).

[lucasjinreal]

Hi, does it can just support by a feature or something, so that cargo install could also do it? I think cargo install is the fastest way to let users use it.

[lucasjinreal]

So you want install copies of large coreutils binaries by default?

I think current make coreutils a binary is ok, as it won't override or effect ssytem commands, but a feature that make coreutils/xx binaries could be more beautiful so that users like me just want override system wide commands, all using rust binary without using coreutils ls etc which takes a lot of time (even set alias is cubersome)

[oech3]

Hi, does it can just support by a feature or something, so that cargo install could also do it?

Impossible with pure cargo's feature, I think. But if you accept long command, long build time and 100 MB+ binaries, you can cargo install uu_true.

[lucasjinreal]

does 100MB binary means each command is a standalone binary