----- On 3 Oct, 2015, at 15:47, Bachsau w...@bachsau.name wrote:
> Clemens Lang wrote on 03.10.2015 15:02: >> such as /bin/sh, /usr/bin/python, /usr/bin/make, /usr/bin/clang, >> etc. > > All of which are also part of macports, so can't you just use this or > create shadowcopies yourself? Yes, we could provide copies of bash, python, make and clang ourselves and use them instead. So far, we have always relied on Apple's toolchain but you're right that we don't really have to. However, remember that it's not just 3-4 binaries we're talking about here. Lots and lots of smaller tools would also be needed, such as ar, as, arch, awk, base64, bc, bison, bzip2, chgrp, chown, cpio, curl, diff, du, grep, fmt, gzip, ... We're currently re-using some of those from /usr/bin to reduce the footprint of our build dependencies. MacPorts is already being criticized for using too much storage and "downloading the internet" before installing what you initially requested, and a change such as this would make things even worse. -- Clemens Lang _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
