Apr 16, 2010, 6:49 AM
Post #26 of 28
May I ask you why you need to *experiment* here, when all this is clearly documented anyway in the man-page of bash (and quite a few other shells)?I guess we disagree on the clarity/readability of manpages.
In this case, a login shell isn't that safe either. While you don't get the parent's environment, you get instead everything which some foreign .profile does. A maintenance nightmare! If I would do this, I wouldn't let bash source *anything*, plus call it from an environment which I control.
Well, the .profiles that we use this way, are in itself version controlled and part of the software to be built. In other words: the .profile controls the versions to be chaked out. So in order to re-produce an arbitrary (old) version of our software, I only need one file: the .profile.
If we could start over again, we'd probably do it different, this is just our way of migrating from a single 'branch' to the ability to have mutiple branches. I happen to work in an industry that doesn't like , major changes...
Let's put an end to this topic, I have my solution, and I agree it's not perfect.