Bug #504713 (cmdline looks for files in 'bin' and not working directory) now affect OS X Yosemite

[RayD at ERISCorp]

I have a fresh install of OS X 10.10 (Yosemite) with a fresh install of Inkscape 0.91 r13725 (Jan 28 2015) and it's essentially unusable from the cmdline because it looks for all relative paths starting from the 'bin' (almost always /Applications/Inkscape.app/Contents/Resources/bin/) directory instead of the current working directory.

I did not have this problem under OS X 10.9 (Mavericks) and the previous version of Inkscape I was running

For example, running:

>pwd
/Users/Me/Documents

>/Applications/Inkscape.app/Contents/Resources/bin/inkscape --file=source.svg --export-png=dest.png -1024 -h 1024

looks for:

Applications/Inkscape.app/Contents/Resources/bin/source.svg

instead of:

/Users/Me/Documents/source.svg

and tries to save the PNG to:

/Applications/Inkscape.app/Contents/Resources/bin/dest.png

instead of:

/Users/Me/Documents/dest.png

EDIT: I just found: https://bugs.launchpad.net/inkscape/+bug/1449251 which seems to be a duplicate. I wonder why the initial search didn't find #1449251

[su_v (suv-lp)]

As explained in the comments of bug #1449251 this is a known problem - the application bundle is not optimized for command line usage (always use absolute paths when referencing any files via cli; or install a regular build e.g. via MacPorts instead if command line usage is the primary use case (e.g. in scripts or Makefiles)) - and already tracked in
* Bug #181639 “Command-line invocation on Mac OSX partially broken”
  https://bugs.launchpad.net/inkscape/+bug/181639