Art,
Though I agree with you, I don't think your tone is justified.
Alas, the problem is not unique to gimp ported through fink. Gimp.app also crashes, as does gimpshop. (In fact, I can't even get gimpshop to launch.) In both cases, the crash happens when I try to make a logo with script-fu. I have a feeling that the problems lies with freetype219. The problems seemed to have appeared when this dependency showed up.
I have managed to avoid rolling back by using other apps to satisfy my rather trivial needs, but if it is imperative that you use gimp, taking these issues up with the maintainer would certainly resolve things much more quickly. I have emailed Alex a few times, and he is quite willing to help.
Cheers, P
PS 2.06 is NOT the stone ages. It's still a highly functional version, don't you think?
------
"...who search the reason of things
Are those who bring the most sorrow on themselves."
--Euripides, The Medea
On May 6, 2005, at 11:32 AM, Art McGee wrote:
OK, let me see if I understand what is going on:
a. Back in April, a reproducible crash was found in GIMP 2.2.4 when using the text/font tool.
b. Because of this, sometime in the last couple of weeks, the Fink port of GIMP was rolled all the way back to 2.0.6.
Now, here are my questions and comments:
1. It would be mighty nice if there was some procedure or method available to give us a little bit more information when packages are rolled back like this. Maybe some text in the database that says "We're sorry, but this is not the most current version of The GIMP. Our port is hosed, so we've rolled you back to the Middle Ages while we work on a fix. If you need the features of the latest version now, consider switching your OS to Linux."
2. Was the crash verifiable on 2.2.4 and 2.2.6? It's unclear why a crash that may have occurred under 2.2.4 has caused us to regress to 2.0.6 instead of advancing forward to 2.2.6.
3. Was it intentional that not only has The GIMP been lost in a time warp, but it's also been broken in such a way that even building the older version is impossible? All I get now are "can't resolve dependecy" and "missing package info" errors.
4. For those who have verified the crash on their machines, did you attempt to replicate it using the precompiled Gimp.app 2.2.6, just to confirm whether the problem is as universal as you believe? If Gimp.app doesn't crash, that may tell us something.
5. Is there any ETA as to when The GIMP will be back to normal and up-to-date?
Art
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
