> > Is it hard to convert the given filenames to their absolute paths in it?
>
> Not possible (because ... the current
> legacy implementation of relocation support
> requires that the actual inkscape binary
> is launched from a specific path inside
> the application bundle, else inkscape
> fails to find and load required shared
> resources looked up at a path relative
> to the application bundle's top-level directory.
> Thus any shell script launcher is required to change
> directory to the top-level directory inside
> the application bundle first,
I'm sure I'm missing something, but I wonder why the launcher can't first convert the filenames given as arguments into their respective absolute paths, before changing directory to the top-level.
> With regard to home-brew casks
> - whatever is offered there is not maintained
> by the inkscape project,
Of course! I mentioned homebrew only because you asked, not in order to complain about it to you.
> > Is it hard to convert the given filenames to their absolute paths in it?
>
> Not possible (because ... the current
> legacy implementation of relocation support
> requires that the actual inkscape binary
> is launched from a specific path inside
> the application bundle, else inkscape
> fails to find and load required shared
> resources looked up at a path relative
> to the application bundle's top-level directory.
> Thus any shell script launcher is required to change
> directory to the top-level directory inside
> the application bundle first,
I'm sure I'm missing something, but I wonder why the launcher can't first convert the filenames given as arguments into their respective absolute paths, before changing directory to the top-level.
> With regard to home-brew casks
> - whatever is offered there is not maintained
> by the inkscape project,
Of course! I mentioned homebrew only because you asked, not in order to complain about it to you.