Re: [Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2
Hi, Thierry Vignaud [EMAIL PROTECTED] writes: gimp2-freetype is already packaged in mandrake contribs since Sun Aug 10 2003 :-) i didn't know that it was for gimp-1.2.x branch. Well, what exactly did you package? gimp2-freetype sounds like it should be working with gimp2 which isn't even released yet, so the package name is certainly bad choosen. Is this built from CVS or from one of the released tarballs? There have been two releases so far: - gimp-freetype-0.2 is for GIMP-1.2 - gimp-freetype-0.3 is for an earlier GIMP-1.3 API and won't work with latest GIMP-1.3 releases I will probably do another gimp-freetype release for GIMP-2.0. However the usefulness of gimp-freetype for GIMP-2.0 is questionable since the text tool has most of its features already (and a few more). Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2
Sven Neumann [EMAIL PROTECTED] writes: gimp2-freetype is already packaged in mandrake contribs since Sun Aug 10 2003 :-) i didn't know that it was for gimp-1.2.x branch. Well, what exactly did you package? i package gimp, gimp-data and gimp1_3. a contributor packaged gimp-freetype-0.4.tar.bz2 as gimp2-freetype which indeed is for gimp2. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp2-freetype
Hi, Thierry Vignaud [EMAIL PROTECTED] writes: i package gimp, gimp-data and gimp1_3. a contributor packaged gimp-freetype-0.4.tar.bz2 as gimp2-freetype which indeed is for gimp2. gimp-freetype-0.4 has never been officially released. I suspect that the package was built from CVS then. If it was built from CVS in August, then it won't work with the latest 1.3 releases. For that reason, I kindly ask you to remove this package. If you want to, you can build a new one based on the current state in CVS, but please don't name it gimp2-freetype until the 2.0 API is completely frozen and it can be sure that the package will indeed work with GIMP-2.0. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp2-freetype
Sven Neumann [EMAIL PROTECTED] writes: Hi, Thierry Vignaud [EMAIL PROTECTED] writes: i package gimp, gimp-data and gimp1_3. a contributor packaged gimp-freetype-0.4.tar.bz2 as gimp2-freetype which indeed is for gimp2. gimp-freetype-0.4 has never been officially released. I suspect that the package was built from CVS then. yes, the package version number explictely said this: gimp2-freetype-0.4-0.20030810.2mdk If it was built from CVS in August, then it won't work with the latest 1.3 releases. For that reason, I kindly ask you to remove this package. If you want to, you can build a new one based on the current state in CVS, but please don't name it gimp2-freetype until the 2.0 API is completely frozen and it can be sure that the package will indeed work with GIMP-2.0. we do not remove packages just because they're build from cvs. being build from cvs rather than an official release does not imply less stability (there're packages for which this is false ...). also some projects do not do official releases for quite a long time despite being stable and usual (eg perl-gtk2 binding which was more usuable and robust than old perl-gtk1 binding). anyway it need to be rebuild for current gimp1.3. abel, götz ? ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp2-freetype
Hi, Thierry Vignaud [EMAIL PROTECTED] writes: we do not remove packages just because they're build from cvs. being build from cvs rather than an official release does not imply less stability (there're packages for which this is false ...). I didn't say this. What I said is that the package definitely doesn't work with the latest GIMP-1.3 releases and that rebuilding the package will not fix this. You will need to use a recent CVS checkout. I also kindly asked you to consider changing the name of the package. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp2-freetype
Sven Neumann [EMAIL PROTECTED] writes: we do not remove packages just because they're build from cvs. being build from cvs rather than an official release does not imply less stability (there're packages for which this is false ...). I didn't say this. What I said is that the package definitely doesn't work with the latest GIMP-1.3 releases and that rebuilding the package will not fix this. You will need to use a recent CVS checkout. and i never said the reverse I also kindly asked you to consider changing the name of the package. i considered it. i gived my opinion. i wille left the final words on initial packagers but i do think that this name nicely show that it's not for gimp-1.2.x. here's why: 1) package coexistance: === since i'll package the 0.2.x version for the gimp-1.2.x branch, the cvs snapthot for gimp1.3.x will either be named gimp1.3-0.4 or gimp2-0.4. since mdk9.2 came with a gimp2-freetype package with hard dependancie on libgimp1.3_20-1.3.20-1mdk, i do not think it's a problem that we've now a new cvs snapshot packaged as gimp2-freetype that require that requires libgimp1.3_23-1.3.23. 2) naming coherency: of course, we can rename it now. but as: - mdk9.2 contribs came with gimp2-freetype - renaming current package would only affect cooker which is just a moving development distro that is not for end users but for cooker developers - gimp-devel stated that gimp-2.x will come soon, so mdk10.0 would provide gimp2 and gimp2-freetype i do not think it's wise to rename this package only in a package repositery that is not used by end users. that would force us to use an epoch tag in that package for no good reason since eventualle the package name would be the same in two consequent mandrake linux releases. we unofficially plan to release mdk10.0 in february. we'll either keep gimp-1.2.x in main and gimp1.3.x in contribs or we'll provide both gimp-1.2.x and gimp-2.0.x in main (and then in next release, gimp-1.2.x would go in contribs or just vanish) after reading gimp-devel, i think the odds're high that gimp-1.3.x will at leat be some gimp-2 pre-release at that time, so i really think that this renaming is uneeded (thus preventing useless moves in spec files cvs module due to package renaming). ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] David's Batch Processor release for Gimp 1.3
Hi, I finally got around to installing Gimp 1.3 and making the necessary changes to DBP, a batch processing plugin for Gimp. The 1.3-compatible version is now available from: http://members.ozemail.com.au/~hodsond/dbp.html Let me know if there are any problems. -- David Hodson -- this night wounds time ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] GIMP at the 20C3
Hi, just a quick mail to let you know that, as usual, a couple of GIMP developers will be hanging out at the annual Chaos Communication Congress: http://www.ccc.de/congress/2003/ So, if you live close enough, consider to join us. Perhaps we can even get a GIMP talk prepared. Or perhaps not, but the event is certainly worth a visit. This year the conference is in a nice new location close to the famous Blinkenlights building. Looking forward to meet you there... Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
