On Thu, 11 Jun 2020 at 19:01, Dirk Eddelbuettel <e...@debian.org> wrote:
> Spot on. And while it's been a while, the _particular_ wisdom of that RH > supplied compiler setup also _required_ sourcing of a shell snippet to set > all appropriate values: PATH, LD_LIBRARY_PATH, ... > > (Astonishing, to say the least, to me that a distribution vendor cannot > integrate the very toolkit it provides so that it is already turned on when > you open a shaell. But as I said, I suspect the target market are > sysadmins > and CTOs not people trying to get work done ...) It's done so that you can have multiple versions of the tools installed side-by-side rather than being blindsided by upgrades breaking your toolchain. This is rather the same justification that the Python community uses for its similarly weird way of selecting from side-by-side Python installations. As someone working to produce regulated environments (to ICH-GxP), this makes sense to me. As someone who has to use both day-to-day, it's a royal pain in the neck! Cheers, - Peter
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
