stty: simplify import

[oech3]

No description provided.

[xtqqczze]

Needs to be rebased on 41f705b to compile.

[oech3]

It is unrelated to passing CI.

[oech3]

I agree with building package using translative dep is not ideal, but I don't think you shoud comment to all PRs if it is not actually broken. cargo build -p uu_stty is possible.

[xtqqczze]

cargo build -p uu_stty is possible.

That's my point though, it doesn't compile:

$ cargo build -q -p uu_stty
error[E0433]: cannot find `fs` in `rustix`
   --> src/uu/stty/src/stty.rs:195:47
    |
195 |                         .custom_flags(rustix::fs::OFlags::NONBLOCK.bits() as i32)
    |                                               ^^ could not find `fs` in `rustix`
    |
note: found an item that was configured out
   --> ~/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustix-1.1.5/src/lib.rs:223:9

[oech3]

OK. I guess macos-latest CI was ignored when rustix::fs was introduced due to slow CI. But other platforms implicitly pulls it.

[xtqqczze]

OK. I guess macos-latest CI was ignored when rustix::fs was introduced due to slow CI. But other platforms implicitly pulls it.

Actually, it was failing to compile on all platforms. It seems we have no CI for non-multicall.

[oech3]

Locally, Linux is not affected.

[xtqqczze]

Interesting, it was failing for x86_64-linux-android.

[xtqqczze]

I like to verify locally with multiple targets at once, e.g.:

cargo check -q -p uu_stty --target aarch64-apple-darwin --target x86_64-linux-android

[sylvestre]

Thanks for your PR