Autopackage installation

[Rowanxmas]

/usr/local/lib/inkscape

fails to be created, so things like ill2svg don't get
installed, and neither do the extensions.

[Bryce Harrington (bryce)]

Confirmed.

The autopackage installs to /usr/lib/inkscape, but Inkscape appears to
be looking in /usr/local/lib/inkscape instead. This path assumption
needs to be altered to find installed extensions in either place.

As a temporary work-around until this is fixed, you can either copy or
symlink /usr/lib/inkscape to /usr/local/lib/inkscape.

[Bryce Harrington (bryce)]

It looks like things may be getting installed to some incorrect places.
Everything in share (including the extensions) gets installed to

    /usr/local/share/inkscape/

That is the standard location that Inkscape should be loading its
extensions from, *not* /usr/local/lib/inkscape nor /usr/lib/inkscape.
Whatever code is putting stuff in those dirs should be deactivated.

[Bryce Harrington (bryce)]

Also note that autopackage is not installing to /usr/local/share/inkscape
but rather to /usr/share/inkscape. So the prefix portion needs to be
accounted for.

[Bryce Harrington (bryce)]

This should now be fixed in CVS. Leaving open until it's been verified
with the next autopackage build.

[Bryce Harrington (bryce)]

There is a different issue now.

After doing:
    rm -rf /usr/local/lib/inkscape
    rm -rf /usr/local/share/inkscape
    rm -rf /usr/lib/inkscape
    rm -rf /usr/share/inkscape

and then installing via autopackage, these dirs exist:

    /usr/lib/inkscape
    /usr/share/inkscape

however when Inkscape is started up, it cannot locate its icons. Doing
this resolves the issue, however:

    ln -s /usr/lib/inkscape /usr/local/lib/inkscape
    ln -s /usr/share/inkscape /usr/local/share/inkscape

[Kees Cook (kees)]

Remember to do autopackage builds with

./configure --enable-binreloc

Many more changes were checked into CVS to generally update
the autopackage code to current versions.

[Kees Cook (kees)]

Seems to be working!