On Wed, Mar 19, 2014 at 11:35 AM, Jason A. Donenfeld <[email protected]> wrote: > On Wed, Mar 19, 2014 at 12:31 PM, Brian Shore <[email protected]> > wrote: >> Also, I don't see any realpath(1) on RHEL6, so this could introduce >> some compatibility issues. > > Thanks for pointing this out! I'd like to use "readlink -f", but this isn't > available on the BSDs. Any suggestion for something broadly supported?
RHEL is probably the only "large" Linux distribution that doesn't have it yet (realpath(1) was added in v8.15). FreeBSD has a realpath(1) but OS X doesn't. OSX can install gnu coreutils to provide greadlink. I think there are enough variations to justify adding this as a shell function in the platform-specific code. Each platform can define "real_path" and implement it as desired (possibly even in pure sh). I would aim for the syntax of realpath(1) without parameters (because they differ between platforms). realpath FILE... If using shell functions as a fall-back, this page seems a good place to start: https://sites.google.com/site/jdisnard/realpath I'm skeptical that his real_path() properly handles a link that refers to a path containing an embedded space. -- Brian Shore Senior Systems Engineer, Security Architect Network Redux, LLC 5200 SW Macadam Ave Ste 450 Portland, Oregon 97239 Desk: 503-274-9905 x503 _______________________________________________ Password-Store mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/password-store
