Just out of curiosity, why would you change to these tools? Because you like to tinker and you're good at it or do they do something different/better than the included tools. Sorry for my ignorance but I always learn new things from you.
Actually there can be good reasons to install the coreutils. For example coreutils’ ln is much more versatile than OSX’s ln.
Anyway there isn’t really a problem: If you install the corutils with homebrew (“gnutls”) they get installed in /usr/local/Cellar/coreutils/ with symlinks in /usr/local/bin, all prefixed with a “g”, that is gcp, gmv, gln etc. So there is no way that they get accidentally used instead of the original cp, mv, ln etc.
They're prefixed, but brew also puts the bin directory for them in your path and symlinks the standard names into it. `which cp` will point to the gcp symlink.
I just removed the coreutils with ‘brew rm -f coreutils’ and reinstalled with ‘brew install coreutils’ and it’s the same as before. All prefixed with “g” and no standard names symlinked to the coreutils.
(Yes the correct name is “coreutils”, not “gnutls” as I stated before.)
Hmm, I have the coreutils installed via homebrew since quite some time, and – just verified – in my /bin directory I have the original cp, mv, etc. (no symlinks).
In my /usr/bin I don’t have any mv, cp, ln, etc. (neither symlinks nor files)
In my /usr/local/bin I don’t have any cp, mv, ln. I *do* have gcp, gmv, gln, all pointing to /usr/local/Cellar/coreutils/8.22/bin/gcp, gmv, gln, etc.
‘which cp’ gives me ‘bin/cp’ which is the original cp. And “/usr/local/bin” is in my interactive path, but it doesn’t matter, because the concerned bins are all named differently (g).
So, either we are talking about different things, or something went wrong with your (or my) Homebrew install of corutils ;-)
Are you sure you installed with Homebrew? Maybe you did reconfigure HB to install to a different directory? Where are your other HB binaries located?
load more (1 remarks)
I haven’t installed GNU Coreutils. I tried Ruby FileUtils with both system Ruby and custom installed Ruby. Moving files with `FileUtils.mv` preserved the tags, but copying files with `FileUtils.cp` lost the tags.
Note mv within a file system should not strip meta data right. Are you just taking about a cross file system mv here? Also it's very surprising that cp -p works, while mv doesn't as they should use the same code. What version of coreutils are you using (mv --version). If this is still an issue, it would be worth reporting to bug-coreutils@gnu.org mentioning the particular extended attribute and version of coreutils.
Remarkbox