On Fri, 20 Aug 2004, herve couvelard wrote:
tom b wrote:
Hello, I'm having problems trying to RPM &/or compile inkscape in Yoper linux. I have a thread going on the Yoper site here: http://www.yoper.com/forum2/index.php?showtopic=1928
Interesting. I've never heard of Yoper. :-)
By the way, there's a page in the Inkscape wiki for posting details about compiling on different platforms, and once you've got it sorted out, you might find it worthwhile to post your notes there:
http://www.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape
No details so far about Yoper, but sometimes a problem (and it's solution) affect other distros, so it might be worth a review.
- I tried the Redhat 0.39 RPM (using KPackage), & got
Failed dependencies: libsigc-1.2.so.5 I compiled that lib sucessfully & put copies in several directories, but still got the same error in KPackage.
well for the rpm in redhat it is normal that inkscape rpm still do not install because of the lack of libsigc, even if you compiled it from source. the rpm system of management knows that there is no libsigc rpm so.... ^^^^
*Nod* Once you do a compile-from-source on one of the dependencies, the inkscape rpm route is not feasible. Ideally, you should locate a libsigc-1.2 rpm package that will install on your distro. Sometimes that isn't possible, though. The options for you at this point are to create your own rpm of libsigc (not a big deal if you've made rpm's before, but a daunting task if you're an rpm-newbie), do an rpm --force --nodeps and pray, or compile Inkscape from source as well.
I usually always opt for the latter option when I hit this point, since that means I can also pull from CVS directly and compile the latest and greatest anyway. :-)
You can also try the autopackage version of Inkscape; that seems to work for some people sometimes, but is a non-rpm approach.
Bryce