Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 02:41 pm, John R. Culleton wrote: upgraded to > version 32.1 That gave problems with both cvs downloads. > > Now I have upgraded to 33 (which comes with the 2.3.1 gimp > tarball BTW) and now stable will compile and install without > complaint. > > I still have the 2.3.1 tarball version in a separate directory > so in an emergency I can recompile in a hurry over there. At this moment I have unstable (2.3.2) compiled and installed and everything seems to be copasetic. The intltool gotcha should be noted by anyone going this route. And of course I had to check date and times and relink gimp and gimp-remote to the latest versions. Thanks to Carol, Sven and Joao among others. Come on in folks, and dive in the pool, the unstable water is fine :) -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 03:59 pm, Joao S. O. Bueno Calligaris wrote: > On Wednesday 29 June 2005 08:40, John R. Culleton wrote: > > On Wednesday 29 June 2005 08:52 am, John R. Culleton wrote: > > > thought it was time to rename the thread since I have gone past > > > the problems with pygtk. > > > > > > If anything else comes up of interest I will report back. > > > > It seems that the error reported earlier prevented final > > compilation so I had unstable splash screens but still the same > > old 2.2 Gimp in actuality. > > > > Back to the drawing board. :<( > > Are you running the program as "gimp-2.3" ? > > "gimp" is just a symbolic link to the actual binary, and the unstable > versions to not replace this link to themselves. That indeed was part of the problem. The rest revolves around intltool. Gim unstable wouldn't take version 30. So I upgraded to version 32.1 That gave problems with both cvs downloads. Now I have upgraded to 33 (which comes with the 2.3.1 gimp tarball BTW) and now stable will compile and install without complaint. I still have the 2.3.1 tarball version in a separate directory so in an emergency I can recompile in a hurry over there. -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wed, Jun 29, 2005 at 12:59:31PM -0300, Joao S. O. Bueno Calligaris wrote: > On Wednesday 29 June 2005 08:40, John R. Culleton wrote: > > On Wednesday 29 June 2005 08:52 am, John R. Culleton wrote: > > > thought it was time to rename the thread since I have gone past > > > the problems with pygtk. > > > > > > If anything else comes up of interest I will report back. > > > > It seems that the error reported earlier prevented final > > compilation so I had unstable splash screens but still the same > > old 2.2 Gimp in actuality. > > > > Back to the drawing board. :<( > > > Are you running the program as "gimp-2.3" ? > > "gimp" is just a symbolic link to the actual binary, and the unstable > versions to not replace this link to themselves. > this is a good point. there is a configure option to make it the default gimp. carol ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wed, Jun 29, 2005 at 04:55:16PM +0100, sam ende wrote: > On Wednesday 29 June 2005 12:40, John R. Culleton wrote: > > > Back to the drawing board. :<( > > poor you :(. i am reading this thread with interest and am thinking of > having a go myself but i am reluctant to do this incase it overwrites my > current installation. can i install, or try to install the gimp 2.2.7 in > a seperate folder/dir which will not interfere or overwrite the current > working version of gimp i have ? > that jumps into advanced building skills. did you get your current installed gimp from a distribution? it should be easy to remove and reinstall such a gimp. carol ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 08:40, John R. Culleton wrote: > On Wednesday 29 June 2005 08:52 am, John R. Culleton wrote: > > thought it was time to rename the thread since I have gone past > > the problems with pygtk. > > > > If anything else comes up of interest I will report back. > > It seems that the error reported earlier prevented final > compilation so I had unstable splash screens but still the same > old 2.2 Gimp in actuality. > > Back to the drawing board. :<( Are you running the program as "gimp-2.3" ? "gimp" is just a symbolic link to the actual binary, and the unstable versions to not replace this link to themselves. ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 12:40, John R. Culleton wrote: > Back to the drawing board. :<( poor you :(. i am reading this thread with interest and am thinking of having a go myself but i am reluctant to do this incase it overwrites my current installation. can i install, or try to install the gimp 2.2.7 in a seperate folder/dir which will not interfere or overwrite the current working version of gimp i have ? sammi ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 08:52 am, John R. Culleton wrote: > thought it was time to rename the thread since I have gone past > the problems with pygtk. > > If anything else comes up of interest I will report back. It seems that the error reported earlier prevented final compilation so I had unstable splash screens but still the same old 2.2 Gimp in actuality. Back to the drawing board. :<( -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
On Wednesday 29 June 2005 01:14 pm, Simon Budig wrote: > John R. Culleton ([EMAIL PROTECTED]) wrote: > > Earlier in my journey autogen.sh had complained about an > > obsolete intltool so I installed version 32 of that package. > > Did you rerun autogen.sh after updating intltool? I removed the cvs/gimp directory ran cvs checkout -r HEAD gimp cd to new gimp subdirectory ran autogen.sh ran make ran make install (pls note post below) > > > BTW I switched from stable cvs to unstable by deleting the > > entire ~/cvs/gimp subdirectory and using the command > > cvs checkout -r HEAD gimp > > > > I used this technique to avoid conflicts between versions. > > > > The initial splash screen for the resulting Gimp says: > > Pixeldumper Developers Release 2.3 > > > > but the window displayed when I click help>about still says > > version 2.2.9 > > It seems you installed the old and the new gimp in the same prefix. > The about dialog should say 2.3.1. > Since I deleted the entire gimp subdirectory I don't see how this could be. > Make sure that you read the file HACKING and INSTALL in CVS. Looking for them now. > > Bye, > Simon -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
John R. Culleton ([EMAIL PROTECTED]) wrote: > Earlier in my journey autogen.sh had complained about an > obsolete intltool so I installed version 32 of that package. Did you rerun autogen.sh after updating intltool? > BTW I switched from stable cvs to unstable by deleting the > entire ~/cvs/gimp subdirectory and using the command > cvs checkout -r HEAD gimp > > I used this technique to avoid conflicts between versions. > > The initial splash screen for the resulting Gimp says: > Pixeldumper Developers Release 2.3 > > but the window displayed when I click help>about still says > version 2.2.9 It seems you installed the old and the new gimp in the same prefix. The about dialog should say 2.3.1. Make sure that you read the file HACKING and INSTALL in CVS. Bye, Simon -- [EMAIL PROTECTED] http://simon.budig.de/ ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: Bleeding edge, WAS [Gimp-user] pygtk and 2.3.1
thought it was time to rename the thread since I have gone past the problems with pygtk. I had a successful cvs/compile/install cycle on Gimp stable. Then I thought I would try Gimp unstable, or bleeding edge. I followed the instructions for CVS of Gimp stable with one modification (see below) I got a working program but this error message stopped the compile: -- Making all in tips make[3]: Entering directory `/usr/local/cvs/gimp/data/tips' ../../intltool-merge ../../po-tips gimp-tips.xml.in gimp-tips.xml -x -u -c ../../po-tips/.intltool-merge-cachemake Possible unintended interpolation of @INTLTOOL_ICONV in string at ../../intltool-merge line 94. Global symbol "@INTLTOOL_ICONV" requires explicit package name at ../../intltool-merge line 94. BEGIN not safe after errors--compilation aborted at ../../intltool-merge line 251. make[3]: *** [gimp-tips.xml] Error 9 make[3]: Leaving directory `/usr/local/cvs/gimp/data/tips' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/cvs/gimp/data' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/cvs/gimp' make: *** [all] Error 2 -- Nevertheless I was able to do a make install, halting at the same spot with the same message. Earlier in my journey autogen.sh had complained about an obsolete intltool so I installed version 32 of that package. BTW I switched from stable cvs to unstable by deleting the entire ~/cvs/gimp subdirectory and using the command cvs checkout -r HEAD gimp I used this technique to avoid conflicts between versions. The initial splash screen for the resulting Gimp says: Pixeldumper Developers Release 2.3 but the window displayed when I click help>about still says version 2.2.9 If anything else comes up of interest I will report back. -- John Culleton ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
