Hi,
Currently Inkscape seems to store a list of extensions it's seen before somewhere, I am not sure where. This causes problems for people who use the autopackages because if they have installed Inkscape before from say apt-get, they probably pulled in various apps along with it like Dia etc and also the plugins. They then install the autopackage and these extensions disappear and now Inkscape gives them an error whenever they start.
I don't think having an extension be removed is really an error, could this behaviour be changed? It's already a preference to not show these logs at startup, maybe it could just default to off?
Also I'm afraid I spotted a stupid bug in the specfile, it was not installing any extensions at all. So here is the 3rd revision of the 0.41 autopackage <sigh>:
http://navi.cx/~mike/inkscape/inkscape-0.41-3.x86.package
Could it be uploaded to SourceForge and the website changed please? Apologies for the inconvenience.
This sort of dumb mistake does remind me why I recommend to others that developers should package their own stuff (a rule I ignored for Inkscape because I needed testing :). I would love for an Inkscape developer - ie somebody who *really* understands this software - to take over maintenance of the autopackages, even if I continue to do the nightly builds.
If nobody is up for it then no matter, I will carry on with it. But I think users would have higher quality packages if a dedicated Inkscape developer were to do it. To give people a taste of what is involved, I pasted the specfile I'm using below. The build system isn't complicated at all. Enhancing the packages would involve doing things like making the gtkspell dependency optional at runtime so it could be enabled, and so on.
thanks -mike
[Meta] RootName: @inkscape.org/inkscape:$SOFTWAREVERSION ShortName: inkscape DisplayName: Inkscape Vector Graphics Editor Summary: Inkscape is an open source SVG editor with capabilities similar to Illustrator, CorelDraw and Visio SoftwareVersion: @VERSION@ Maintainer: The Inkscape team inkscape-devel@lists.sourceforge.net Packager: Mike Hearn <mike@...333...> PackageVersion: 3 AutopackageTarget: 1.0
[Description] Inkscape is an open source SVG editor with capabilities similar to Illustrator, CorelDraw, Visio, etc. Supported SVG features include basic shapes, paths, text, alpha blending, transforms, gradients, node editing, svg-to-png export, grouping, and more.
[BuildPrepare] if [ ! -x configure ]; then ./autogen.sh fi export APBUILD_STATIC="popt=$source_dir/autopackage/libpopt.a gc gccpp" export LDFLAGS="-L/home/mike/static/lib" export PKG_CONFIG_PATH=/home/mike/static/lib/pkgconfig prepareBuild --enable-binreloc
[BuildUnprepare] unprepareBuild
[Imports] echo '*' | import # import everything
[Prepare] require @gnu.org/libstdc++ 3 require @xmlsoft.org/libxml2 2.6 require @xmlsoft.org/libxslt 1.0 require @gtk.org/gtk 2.4 # statically linked for now: require @rpm.org/popt 0.0 # statically linked: require @libsigc.sourceforge.net/libsigc 3 require @libpng.org/libpng 3 # statically linked: require @gtkmm.org/gtkmm2 3 require @zlib.org/zlib 1
[Install] installExe bin/inkscape bin/inkview installMan 1 man/man1/* installIcon share/pixmaps/inkscape.png installDesktop "Graphics" share/applications/inkscape.desktop copyFiles --nobackup share/locale $PREFIX/share copyFiles share/inkscape $PREFIX/share copyFiles lib/inkscape $PREFIX/lib
[Uninstall] uninstallFromLog
Hi all.
On Tue, 29 Mar 2005 17:12:41 +0100, Mike Hearn <mike@...333...> wrote: [...]
Also I'm afraid I spotted a stupid bug in the specfile, it was not installing any extensions at all. So here is the 3rd revision of the 0.41 autopackage <sigh>:
http://navi.cx/~mike/inkscape/inkscape-0.41-3.x86.package
Could it be uploaded to SourceForge and the website changed please? Apologies for the inconvenience.
[...]
I just uploaded the file to SourceForge. The inkscape-0.41-2.x86.package has not been deleted from the file list because the website still points to it. Someone with access to the website should please update it.
Greetings!
Daniel Díaz yosoy@...31...
Hi Guys, been trying to look into some of the extension related problems people have been having, particularly from a windows point of view, and found that one of the hardest things was just working out what depended on what, so i've drawn a fairly ugly tree up to indicate the dependancies. I've not included the stuff that ships with Inkscape, like the scripts themselves, but have stuck to the issues that will affect inkscape assuming its been properly packaged and distributed. I've commented on some of the issues that we have wrt windows. Even with one that should be workable tho, (the wmf one) I'm not having any joy. Its installed, it works from the command line, and is in the path, but doesnt get detected by IS. I tried changing the dependancy to wmf2svg.exe but that didnt work, I tried deleting the dependancy, which puts it in the menu, but throws an error about the file being null.
any suggestions would be welcome.
Cheers
John
__________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs
On Tue, 2005-03-29 at 14:13 -0800, John Cliff wrote:
I've commented on some of the issues that we have wrt windows. Even with one that should be workable tho, (the wmf one) I'm not having any joy. Its installed, it works from the command line, and is in the path, but doesnt get detected by IS. I tried changing the dependancy to wmf2svg.exe but that didnt work, I tried deleting the dependancy, which puts it in the menu, but throws an error about the file being null.
Did you try changing the <script><command> section to have the .exe also? Perhaps the path parsing is wrong... you said that the wmf2svg.exe is in your path right? Is the G_SEARCHPATH_SEPARATOR correct on win32? I thought using that would make the path search "cross-platform", but perhaps it is not?
That code is all in: src/extension/dependency.cpp: Dependency::check()
It might take some instrumentation to figure out what is going on :(
--Ted
Ted Gould wrote:
That code is all in:
src/extension/dependency.cpp: Dependency::check()
It might take some instrumentation to figure out what is going on :(
Some of that might come out of my refactoring for the dialogs. So if things aren't settled by this weekednd, I'll take a peek at getting things done that could help in this case also.
participants (6)
-
Bob Jamison
-
Daniel Díaz
-
John Cliff
-
Jon A. Cruz
-
Mike Hearn
-
Ted Gould