Closed robinwhittleton closed 7 years ago
I'd be happy for the script to work on Mac, but I don't have one to test on--I run Linux exclusively. If you're able to fix it so that it runs on both, that would be appreciated.
The long-term goal is to have all of these tools converted to Python scripts instead of Bash. build
is low on the list because it's so complicated.
Any issues due to differences between the standard tools on Linux and macOS would likely also be shared with other BSDs. Not that there's a lot of people running FreeBSD on their desktop, but they're extremely common for servers.
Additionally, rather than using a VM, it would probably be easier to install the GNU coreutils. Very easy to do using homebrew or pkg/ports.
Fwiw I’ve basically moved my SE production over to an Ubuntu VM. I’ve got most of the intermediate stages working (although potential for bugs remain) but build is completely broken and I’m not sure how to get it working - base64 for example is a completely different program in homebrew vs ubuntu. Probably the best bet at this point is to wait for the Python overhaul.
On 20 Jun 2017, at 14:43, Rob Speed notifications@github.com wrote:
Any issues due to differences between the standard tools on Linux and macOS would likely also be shared with other BSDs.
― You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I’m happy to close this, given the difficulty of fixing, now that the README notes mac incompatibilities: https://github.com/standardebooks/tools/commit/653e43d3821a3f63bb4003caa89efd59ad3be6db
Combination of extended attributes for
cp
/rm
and a reliance on-e
/-q
flags for xpath. The extended attributes seem to be easily replaced with the shorthand (e.g.--recursive
to-r
), xpath seems to support a fixed argument order (filename then expression rather than using-e
). I’m gradually fixing these up locally, but I’m not sure if macOS is even a desired platform for building.