Bernd Haug wrote: > Dave Howorth wrote: >> Programs are not generally built with absolute paths. > > Not in my experience - many custom build scripts modify headers with > absolute paths. > > Or think of even the many automake builds where --prefix influences > the build stage.
If they use absolute paths embedded in code, they are poorly written scripts, IMHO. The number of days I've wasted over the years dealing with that kind of idiocy is more than I can remember. > Generally, that's intended. Suppose you have a stable and an > experimental version of dirvish running; you want each one's runall > call *their* dirvish, not the onle that happens to be in path. Thank you, you make my point :) You can do this with Dirvish, but it does NOT use absolute paths in the code. dirvish-runall reads configuration, either from a file or from the command line and uses that to determine where to find dirvish. Only if you don't tell it, does it default to using the environment path. And even then, you can set that path in the shell prior to calling dirvish-runall. No absolute paths in the code. Cheers, Dave _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
