Hello all,
In my attempt at being able to build CVS once again and upgrading to Fedora Core 2 from FC1 (intermediate b4 gentoo), I found several errors which many users and developers have been complaining about not working.
Upon some research and acting as JoeUser, it appears that this collector is not available as an RPM or common package!!! I'm reacting to this as JOE USER and this is probably not good for our next release.
There are only old rpms for SUSE available and Bryce has tried (and they did not work). Also, Ted says that this garbage collector is avail. for debian. But, there are not packages available for Fedora Core as far as I can see and not many listings elsewhere.
Thus, we really need this to be more widely available. There are three options I see:
1.) EASY: Drop Boehm Garbage Collector as a dependency (or replace with something more widely avail)
2.) MED: Push changes upstream and try and get packages for current version of this collector at common repositories.
3.) HARD: Supply our own along with Inkscape as a package or in our main build tree.
Please voice your opinions, as our current dependencies are a little too bleeding edge it seems right now, and I totally understand why these are needed. However, if by the time we do a release these dependencies are not widely available on the dominant distros (fedora core, windows, etc), then there will be a problem (aka, loss of users).
Thoughts and solutions?
Jon
Thus, we really need this to be more widely available. There are three options I see:
The best we can do is to link it statically, so those using binaries won't even notice. Those compiling from source will have to compile gc from source - it's small and easy (provided you know where to find it and which version to use, which must be documented).
Aha, so after pushing on gtk+ 2.4 changes on freenode #fink, found out that the Boehm Garbage Collector is also called:
* libgc-devel * gc * libgc
So, it looks to be widely available, but under diff. names. I think the best approach is to push with package maintainers of various systems and distros to get most stable recent versions of gtkmm. I have done this with FINK (http://fink.sf.net) and this seems to work, as they respect the developer to developer upstream connection. :) Others might try this for their respective distro (fedora, etc) as we add more dependencies in the future.
I've been addind my findings to this wiki on fedora core 2 and the new dependencies: http://inkscape.org/cgi-bin/wiki.pl?CompilingInkscape
Jon
On Sun, 2004-08-01 at 17:12, bulia byak wrote:
Thus, we really need this to be more widely available. There are three options I see:
The best we can do is to link it statically, so those using binaries won't even notice. Those compiling from source will have to compile gc from source - it's small and easy (provided you know where to find it and which version to use, which must be documented).
Jon Phillips wrote:
3.) HARD: Supply our own along with Inkscape as a package or in our main build tree.
Amen!!!!
I have always said that we should
1) Either link statically with hard-to-find libs, or..... 2) Provide it ourselves.
This is not an issue for a while, of course. Joe User will not be knocking on our door until 0.40 is released.
Bob
participants (3)
-
Bob Jamison -
bulia byak -
Jon Phillips