3 ms·
I'm not going to comment about cygwin (because its build process is not as transparent) but instead about msys2, the spiritual successor to cygwin. See for you
by frutiger 11y ago
I'm not going to comment about cygwin (because its build process is not as transparent) but instead about msys2, the spiritual successor to cygwin. See for yourself: https://github.com/Alexpux/MSYS2-packages/blob/master/coreutils/PKGBUILD https://github.com/Alexpux/MSYS2-packages/blob/master/coreut... is the `pacman` style `PKGBUILD` used to build the `coreutils` package.
- dikaiosune 11y agoThat looks pretty clean, but they're still applying looks like 5 patches which would need to be maintained separately. It's certainly not as bad as a full port, but it's still not the same codebase. Rust's cross-platform efforts would (I think?) obviate that process.
- kazinator 11y agoBut, nevertheless, it's not exactly a port of Coreutils to Windows per se. For instance, let's take the "cp" utility. A Windows port "cp" should be able to copy Windows-specific file attributes. Does the Cygwin "cp" do that? How about NTFS forks? I don't believe that you can write some portable code in Rust, and have a "cp" utility which correctly handles every quirk of every OS's file structure.
- dikaiosune 11y agoNot familiar with Windows' filesystem APIs, but the description for the Rust function in the stdlib is here: https://doc.rust-lang.org/std/fs/fn.copy.html https://doc.rust-lang.org/std/fs/fn.copy.html Seems like it should handle platform specific attributes?