From: Dave W. <dw-...@di...> - 2008-04-03 06:44:16
|
Eero Tamminen wrote: > > "Global" environment of the current process and its children. It doesn't > propagate to other processes of even the same user (among other things that > would be a security hole as environment variables are used to control many > dynamic library loading features of the Glibc dynamic linker, Gtk etc). Yes, correct, but export does effect the shell that ran the script, which is what I was trying (poorly) to say. Obviously need to work on that part some more. >> What about relative paths? They seem to appear exactly as typed, >> which would cause GRAMPSHOME to be a relative path. Do you think it >> would be ok to drop the 'cd' and allow GRAMPSHOME to be relative to pwd >> (and perhaps even just '.')? Might that cause problems somehow? > > No idea. :-) My testing shows that using a relative path to the script works fine, even in the extreme case where GRAMPSHOME is just '.' (IF the script doesn't do a 'cd'). GRAMPS doesn't appear to ever do chdir, so that shouldn't be a problem. So I removed the 'cd' and the warning about relative paths. > So... "${0%/*}" means: > - take the value of variable $0 > - remove from the end ('%') part of it... > - ...the part matching to glob pattern "/*" > i.e. the last '/' character and anything following it. Awesome! I never knew you could do that! And your rename script is great. I've really needed that a few times... Anyway, I've put in all your suggestions and tried to improve the discussion of the environment stuff. See how that looks to you. Thanks for the improvements! Dave |