On Mon, 19 Jul 2004, Gazal, Geraud (MED) wrote:
Either Wiki or CVS would be suitable places for storing it. There are roughly equal pros and cons both ways. Wiki would be more widely accessible to more people, but CVS would allow a little more flexibility for manipulating the document (e.g., grep, txt2pdf, etc.)
-> workaround : HTML format ( portable, plus support usefull things such as images, links, tables...) maintained in the CVS and linked to a wiki page ?
HTML maintained in CVS would work fine. We can use a subdir in the inkscape_web module, and link to it from the Documentation page; no need for Wiki to be involved.
Tests: Build Linux (Debian / Gentoo / Slackware / Mandrake / Fedora
/ Suse / Others)
Windows (98 / 2000 / XP) MacOS (X) BSD (Free / Open) Other Unices (Solaris / Irix)Note that an important condition for distros is what installation options were used. For example, a pure-base SuSE installation will not include developer tools like gcc. Most distros also have installation options which will end up lacking the -devel libs that Inkscape needs to compile. So each of these will require specification as to which installation options must be used during setup.
Argh, sounds complicated. The best thing, I suppose is to identify a maintainer by distro (ala Mandrake) and ask them to write down the specs for their respective distro
Let's think on this some more. I think it is possible to programmatically extract this sort of info from the package for that system. Being able to automatically test the dependency needs for various platforms would be extremely useful (and would be useful to other programs beyond Inkscape), but would take a good bit of work to figure out how to do it. Put this a bit lower in the priorities, and let's think about it a while.
Notice : should be automated (example see : http://public.kitware.com/Dart/HTML/Index.shtml)
Interesting - have you used this system?
Yes, that's why I was thinking about it :) But I'm trying to find even better and flexible
I'd like to get more info from you on it. We (at OSDL) have a similar framework that we're developing, called STP. I'd be interested to see how Dart stacks up to it.
- provide a shaker tool (this tool would launchInkscape and then start
a predefined number of pseudo-random commands -logging each
action). The
goal is to detect crashes and analyse their conditions with the logs
Another idea along these lines is to fire a variety of signals at it, and detect if it behaves correctly.
Just need a few precisions so that I understand better
There are a variety of signals you can send a program to cause it to do various things. `kill -9` (or kill -KILL) is one example. Some others:
{bryce@...347...} ~/src/Stp (185): kill -l HUP INT QUIT ILL TRAP ABRT BUS FPE KILL USR1 SEGV USR2 PIPE ALRM TERM STKFLT CHLD CONT STOP TSTP TTIN TTOU URG XCPU XFSZ VTALRM PROF WINCH POLL PWR SYS RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX
What should Inkscape do when you throw one of those signals at it? What does it do? This could be a simple thing to test.
Bryce