On 2006-December-11 , at 21:03 , Bryce Harrington wrote:
On Mon, Dec 11, 2006 at 03:28:10PM +1100, Michael Wybrow wrote:
On Sat, 9 Dec 2006, MenTaLguY wrote:
On Thu, 2006-12-07 at 09:15 -0800, Bryce Harrington wrote:
Thus, I think we've given more than adequate wait time for Fink to upgrade to 2.8. Given that there is a new issue which necessitate going to gtk 2.8 now, I'd propose that we drop the previous agreement and move up the gtk version for this release.
My feeling is not to wait on fink any longer and just go ahead and update Inkscape to depend on GTK 2.8. The pool of people compiling Inkscape on OSX seems small enough that we can switch to a different method involving a custom script or via DarwinPorts if anyone wants to investigate that.
Sounds good, it looks like there is roughly a concensus favoring this approach, so we should go ahead with this plan.
Just to mention it, I think it would be better/more efficient to use DarwinPorts than to have a custom additional install for Inkscape. I am conscious that people will do what they like (and that is what is great with an open source project!) so let me explain my reasons and try to convince you. A custom install means: - additional disk space resources (this is not expensive but that is still something) - additional compilation time for Inkscape only (once in a while but still) - additional maintenance burden on Inkscape and Mac OS X Inkscape compilers side - some work that won't benefit any other project than Inkscape On the other hand, using DarwinPorts means: - that the maintenance work is done by the DP team, not Inskcape - every installed package could be used for other applications. I think it is very likely that Inkscape developers use other GTK applications present in DarwinPorts (eg. Gimp, Agave,...) so they will install GTK via DarwinPorts anyway. Therefore compilation time and disk resources won't be used for Inkscape only. - updates are easy
So I think thats using a custom install script to resolve Inkscape dependencies is much work to solve a problem for which elegant solutions already exist, unless we use a version of GTK that is not in DarwinPorts (which is not the case now and probably won't ever be because DarwinPorts is evolving quite rapidly), or unless the custom work ends in providing GTK in a reusable form (eg. as a .framework) which could benefit other projects (but is probably a bit out of Inkscape's scope). When we discussed this earlier, somebody (I think it was Jon Cruz) mentioned that not using Fink or DarwinPorts to resolve Inkscape dependencies would be just like ditching apt on a Debian box (or yum on a Fedora or...). This is something that you probably don't want to do unless you have very exotic needs (use svn versions of some packages, use specific compilation options etc.). Again, I won't refrain anybody from doing it but, as an occasional Inkscape compiler, I would prefer Inkscape to integrate with my existing DarwinPorts install than to have to compile and install all of GTK a second time.
JiHO --- http://jo.irisson.free.fr/