Btw, there was one issue I found in the inkscape.spec file that other RPM packagers will need to look to as well:
* Remove the following line from the spec file:
%{_libdir}/inkscape/extensions/*
We have consolodated extensions into the /usr/share/inkscape directory with the other data files.
Bryce
On Sat, Jul 17, 2004 at 03:25:11PM -0700, Bryce Harrington wrote:
Btw, there was one issue I found in the inkscape.spec file that other RPM packagers will need to look to as well:
Remove the following line from the spec file:
%{_libdir}/inkscape/extensions/*
We have consolodated extensions into the /usr/share/inkscape directory with the other data files.
Since the .inkmod files are arch-independent, this is okay. However, once we actually have arch-specific .so files, etc, they need to go back into lib, to follow the linux fs rules.
On Sat, 17 Jul 2004, Kees Cook wrote:
On Sat, Jul 17, 2004 at 03:25:11PM -0700, Bryce Harrington wrote:
Btw, there was one issue I found in the inkscape.spec file that other RPM packagers will need to look to as well:
Remove the following line from the spec file:
%{_libdir}/inkscape/extensions/*
We have consolodated extensions into the /usr/share/inkscape directory with the other data files.
Since the .inkmod files are arch-independent, this is okay. However, once we actually have arch-specific .so files, etc, they need to go back into lib, to follow the linux fs rules.
Note that when we do this, we probably ought to be forward-thinking and establish a version-oriented structure like Gimp does:
/usr/lib/gimp/1.2/modules/ /plugins/
which for us might look like:
/usr/lib/inkscape/0.40/extensions/plugins/ /library/ /scripts/ /1.00/extensions/plugins/ /library/ /scripts/
Bryce
participants (2)
-
Bryce Harrington -
Kees Cook