> As rock developer I have to understand the installation process, e.g., to be > able to repair installations and thus I sometimes also take advantage of this > knowledge.
If you wonder about the installation process details, ask. After enough questions you should have an idea of how the installation process is *meant* to work which is a more actionable information. The three lines that you find so transparent are full of red flags: 1. manually set GEM_HOME (without setting GEM_PATH I might add) 2. access a hidden folder 3. run an unrelated command to hopefully initialize the autoproj environment (envsh) (1) and (2) place a lot of assumptions on autoproj's internals. How do you know whether these assumptions actually match autoproj's, or if you're doing something that works by accident ? (3) is in effect exploiting a bug in autoproj. So, my apologies if it felt like I was trying to stifle your free speech, but even if it feels better to you to go close to the metal, this is *not* good practice. Sylvain _______________________________________________ Rock-dev mailing list Rock-dev@dfki.de http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
