4 ms·
GNU's sed is probably portable to every platform that glibc is ported to (and if somehow it isn't, it is almost certainly trivial to fix; I've never had problem
by saurik 14y ago
GNU's sed is probably portable to every platform that glibc is ported to (and if somehow it isn't, it is almost certainly trivial to fix; I've never had problems compiling sed for systems I work with). I thereby fail to see the reason to burn even a single extra neuron on behalf of the people having to maintain the glibc build system to deal with possible incompatibilities that might come up between different versions of sed at build time.
- comex 14y agobecause requiring a user to find and install an external project just to avoid thinking about possible incompatibilities in what is almost certainly a set of simple uses of a standard tool is a waste of his time.
- saurik 14y agoIn what universe is it difficult to install sed? It is so simple to do you could automate it, which is why it is already automated on the systems these people are discussing, such as FreeBSD: just port install gsed. We are talking about build time here: if you are building a project and are unwilling to do the braindead task of installing dependencies then very very honestly you shouldn't be installing glibc in the first place, as busybox comes with its own libc that can be used instead, and there is already a libc on every one of these other systems, so by your logic someone else is already wasting your time.
- deleted 14y ago[deleted]
- saurik 14y agoYes, I've read that (and didn't consider it very enlightening); however, the argument in that article would actually argue against the notion that there needs to be a million versions of sed in the first place, and that the hacks required to maintain compatibility with a million different versions of sed is actually a design debt that was caused by the bazaar's lack of central organization sufficiently intelligent enough to standardize on one version of sed.