- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] URGENT: Please update Mac OS X install instructions in the tarball !
by Ted Gould 30 Nov '09

30 Nov '09

Wolf, Thanks for this. I went ahead and pushed it into a branch with a merge request. Does that look right? For all the OSX folks on the list? (I made one merge request for 0.47 branch, but it should go both there and on trunk) https://code.launchpad.net/~inkscape.dev/inkscape/readme-update https://code.launchpad.net/~inkscape.dev/inkscape/readme-update/+merge/15433 --Ted On Mon, 2009-11-30 at 13:24 +0100, Wolf Drechsel wrote: > > > I am very grateful that a lot of people invested lots of time in > > > the > > > wonderful packaging/macosx/osx-build.sh script. > > > > > > > > > PLEASE, add a few lines to the READMEs - or create a > > > distinguished > > > "README_Mac_OS_X" to make clear, that the install procedure on a > > > Mac > > > is a different one. > > > > > > Could you propose what should be added to the README. I think it's > > a > > good idea to update it, but I'm afraid that I would write something > > incorrect if I tried as I have no experience on OSX. > > > I'll be happy to give it a try - could friend ~suv have a look on it > in order to avoid greater portions of nonsense please ? > > > I suggest to change this chapter of the README: > > > > Inkscape uses the standard procedure for compilation and > > installation: > > > > > > ./configure > > make > > make install > > > > > > If a "./configure" file is not present, you can create it by running > > the "./autogen.sh" command, which calls in turn a number of other > > programs such as automake and autoconf. See INSTALL for more > > details. > > > into: > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for *nixes (Mac OS X users please have a look at the end > of the file): > ========================================================== > > > Inkscape uses the standard procedure for compilation and > installation: > > > ./configure > make > make install > > > If a "./configure" file is not present, you can create it by running > the "./autogen.sh" command, which calls in turn a number of other > programs such as automake and autoconf. See INSTALL for more > details. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > At end of file: > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for Mac OS X users > ======================= > > > We try to keep the Wiki pages on compiling inkscape up-to-date and > comprehensive. It is here: > > > http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX > > > For a brief overlook: > We suggest to use macports (http://macports.org) in order to achieve > all the necessary components and libraries. Than there is a mighty > tool called "osx-build.sh" in the packaging/macosx directory of the > unpacked tarball. This script will do most of the work for you. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > In the INSTALL file change: > > > > Basic Installation > > ================== > > > > > > If you have problems compiling Inkscape, then see > > http://wiki.inkscape.org/wiki/index.php/CompilingInkscape .. > > > > > > The remainder of this file gives generic installation instructions. > > > into > > > > > Basic Installation for *nixes - Mac OS X users please have a look > > > at the README > > > =========================================================== > > > > > > > > > If you have problems compiling Inkscape, then see > > > http://wiki.inkscape.org/wiki/index.php/CompilingInkscape > > > > > > > > > if you are a Mac OS X user, please dont read on, keep to the wiki > > > pages instead: > > > http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX > > > > > > > > > The remainder of this file gives generic installation > > > instructions. > > > … > > > > > > > >

1 0

bzr repo link on the web
by Alexandre Prokoudine 30 Nov '09

30 Nov '09

Hi, Could somebody please update download page at inkscape.org to reflect the switch to bzr/lp and provide a simple command line that doe sit? Currently it takes a hell of time to figure out how to fetch repository. Alexandre

1 0

GSoC Node Tool branch published
by Krzysztof Kosiński 30 Nov '09

30 Nov '09

Hello all If anyone wants to check out the rewritten node tool: bzr checkout lp:~tweenk/inkscape/gsoc-node-tool Send me any GDB dumps of crashes, feature requests, regression reports or usability glitches you find. Regards, Krzysztof

4 5

.bzrignore file
by Maximilian Albert 29 Nov '09

29 Nov '09

Hi all, first of all, many thanks to everyone involved for their release work on 0.47 and the conversion of the repository to bzr! Good job!! I just did my first cautios steps in playing with the new repo and bzr, and I was wondering whether it's really a good idea to put the file .bzrignore under version control. For after checking out trunk and compiling, I've ended up with a lot of files that are neither under version control nor currently present in .bzrignore and thus totally clutter the output of 'bzr status'. But if I add them to .bzrignore then I need to be careful not accidentally commit the file (because surely we don't want every developer to add more stuff to .bzrignore which may only be relevant to his/her specific checkout). So wouldn't it be better to not provide a 'central' .bzrignore file and let the developers create local ones instead if desired? Thanks for any opinions, Max

3 2

Bazaar repository error
by Krzysztof Kosiński 29 Nov '09

29 Nov '09

Hello I tried to push the node tool work to Launchpad, and I get this: bzr: ERROR: KnitRepository('lp-46092624:///~inkscape.dev/inkscape/trunk/.bzr/repository') is not compatible with CHKInventoryRepository('lp-46092624:///~tweenk/inkscape/gsoc-node-tool/.bzr/repository') different serializers Would a 'bzr upgrade' on the Launchpad repository fix this? Regards, Krzysztof

4 5

0.47 tarballs
by Ted Gould 29 Nov '09

29 Nov '09

Hello All, I have built and put up 0.47 tarballs on Sourceforge. I'll start by reminding everyone to not widely announce this yet, we'll wait for binaries to be available before doing so. Also, sorry to take so long on this, I was away from home for work but I'm back now :) https://sourceforge.net/projects/inkscape/files/inkscape/0.47/ I'll tag everything and update that stuff tomorrow (as I'm tired now) but the tarball is correct. --Ted == MD5 Sums == 7b497c8f673e40b05295a29f6e2111f4 inkscape-0.47.tar.bz2 79e83b29956727e8c86a27f815d71f76 inkscape-0.47.tar.bz2.asc 916c85b501bcfb0ae61fcf7318f36348 inkscape-0.47.tar.gz 95bc78c1c24262dd8f89c347a1ffdc5a inkscape-0.47.tar.gz.asc 64e59540374de68dd81eaabedca741dc inkscape-0.47.zip fbc4affd7bcc88453abb5f13b279d45e inkscape-0.47.zip.asc == SHA1 Sums == 7c75352f3882ebf4fcaebc22413bcb79bf3b7895 inkscape-0.47.tar.bz2 d2633fcd7451b7d1b98e0aa139890c960ef504ed inkscape-0.47.tar.bz2.asc aa39d5f7306edb21be4987651041bf50c13baf75 inkscape-0.47.tar.gz 2f6a238a606906822f11f162d95dd1876028f2f6 inkscape-0.47.tar.gz.asc d838901d8312a3e88e8a16f8e4710d923c89567c inkscape-0.47.zip d595cca3f55bab899b33905f35f087f67811445c inkscape-0.47.zip.asc

8 18

URGENT: Please update Mac OS X install instructions in the tarball !
by Wolf Drechsel 29 Nov '09

29 Nov '09

Hello, I want to repeat a request I stated a time ago: From my experience (which was graciously shared by ~suv), the present state of install instructions for Mac OS X is extremely misleading and can cause people to waste a lot of time. When a less experienced person downloads the tarball, he will tend to read the README, which will tell him: > Inkscape uses the standard procedure for compilation and installation: > > ./configure > make > make install When trying this, this man will run into trouble. I am very grateful that a lot of people invested lots of time in the wonderful packaging/macosx/osx-build.sh script. PLEASE, add a few lines to the READMEs - or create a distinguished "README_Mac_OS_X" to make clear, that the install procedure on a Mac is a different one. At this occasion the wiki entries should be revised. At least concerning the inkscape aqua affairs, the wiki is quite outdated; I added instructions which worked on my Mac. I think, using the osx- build.sh it's very simple now, it would be a pity to let things occur more complicated than they are in fact… Thanks and greetings, Wolf

2 1

Extension Repo
by Chris Mohler 29 Nov '09

29 Nov '09

Hi all, I was thinking about starting on an extension repo[0], and have a couple of questions. Should this be hosted by the Inkscape project? If so, how do I go about getting access? Or at least finding out what version of php/python/mysql are available to set up a local test site? If not, is anyone willing to pool resources for hosting? Or know of a good FOSS-friendly place to host? Any thoughts or opinions on server/language/db? I'm leaning toward apache/php/mysql, but something like cherrypy/python/sqlite would be well suited to this task as well. Thanks, Chris [0] http://wiki.inkscape.org/wiki/index.php/ExtensionsRepository

6 6

please provide support for graphicsmagick
by Dennis Heuer 29 Nov '09

29 Nov '09

hello inkscape supports imagemagick, which is nowadays usable but had a lot of issues. this is why i switched to graphicsmagick, a faster and more reliable (maintained) port of it. please consider supporting graphicsmagick. except of the names, both expose the same api. many thanks -- GorgonZola <gorgonzola@...1955...>

3 2

inkscape vs. vanilla system
by unknown＠example.com 29 Nov '09

29 Nov '09

seems that inkscape doesn't like to install on an up-to-date vanilla system. it relies too much on distro defaults. first, python is not found because the path searched at is not existing. it is not mentioned in any file on my system. python-config doesn't spit it out either: configure:9578: g++ -o conftest -g -O2 -fopenmp -Werror=format-security -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp -lgc /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so -lpthread -ldl -lutil >&5 g++: /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so: No such file or directory the point is that "python2.5/config/" is a redundant fiction. also, i re-installed poppler with support for the unsupported xpdf headers. inkscape still didn't compile. then i turned off poppler support, which was also confirmed in the configuration overview. however, it is still used. and, the way it is used seems to be targeting at an older version: extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetExtGState(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:812: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1012: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1014: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1035: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1037: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1104: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1148: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opShFill(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1546: error: no matching function for call to 'GfxResources::lookupShading (char*)' /usr/include/poppler/Gfx.h:114: note: candidates are: GfxShading* GfxResources::lookupShading(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doImage(Object*, Stream*, GBool)': extension/internal/pdfinput/pdf-parser.cpp:2510: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:2595: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doForm(Object*)': extension/internal/pdfinput/pdf-parser.cpp:2770: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) i now tried the compilation process several times, always getting stuck, and always getting stuck after about half an hour. possibly you should port inkscape to "go" to make it break faster. also, if anybody wants to help me in this case, your surname should not be alexandre. many thanks. -- GorgonZola <gorgonzola@...1955...>

2 1