On 2009-January-07 , at 19:06 , step21 wrote:
@jiho looking at the python script and the gimp way, but for ex. the python script for me just says ":: mkdir -p Inkscape.app/Contents/Frameworks/" and I didn't look more closely at it yet after that.
ok, not a good start :/
As for the gimp build: I'd rather make it work properly with my current macports install, (apart from maybe deactivating/activating one port or another) both for HD constraint reasons (macports is on / which is only 80 GB in my case, and that can't change) (though ofc it might be the better way if I had a dedicated machine for that)
yeah, their symlink and dedicated macport install seems a bit weird and overkill to me. I'm glad to know that I'm not the only one thinking that now ;)
[...] and it seems to handle the creation of actual installers for mac software, which really shouldn't be necessary for inkscape
indeed we don't want that, at least not until there is a common GTK framework that gets installed for all GTK apps.
I uploaded the most recent package I made (probably far from perfect but I need some testers) to http://rapidshare.com/files/180771457/Inkscape_2_.dmg [...]So if any mac users are readings this, please test this.
I'll test that on Leopard Intel. What's your macport prefix, the usual /opt/local? If yes I'll move mine while I test to be sure there's no link to there left in you app bundle.
(btw, anything less than leopard is even less tested, I'm not sure about ppc, but probably won't work either)
If you have not explicitly specified the +universal flag while building stuff with macports, then it surely won't be universal.
JiHO --- http://jo.irisson.free.fr/