Re: [Gimp-developer] GNU/Linux vs. Linux

2002-04-04 Thread Thierry Vignaud
Roger Leigh [EMAIL PROTECTED] writes: so should we speak of gnu-bsd-mpl-qpl-artistic/linux ? or, as gpl softwares number is greater than gnu/fsf ones, should we speak of gpl/linux ? A distribution is much more than an operation system. If you just look at the core components that make

Re: [Gimp-developer] GNU/Linux vs. Linux

2002-04-08 Thread Thierry Vignaud
Simon Budig [EMAIL PROTECTED] writes: We should change it - to Unix. registered trademark :-( -- Still untested beyond 'it compiles' (davej) ___ Gimp-developer mailing list [EMAIL PROTECTED]

[Gimp-developer] [PATCH] mandrake patches dump

2002-06-11 Thread Thierry Vignaud
hello, i'm the gimp maintainer in mandrake linux distribution. here're the patches i currently apply on gimp-1.2.3: explaination note for a default that make perl programmers behave strangely with gimp. by default, gimp perl modules doesn't export functions, which makes perl programmers became

Re: [Gimp-developer] [PATCH] mandrake patches dump

2002-06-11 Thread Thierry Vignaud
Sven Neumann [EMAIL PROTECTED] writes: explaination note for a default that make perl programmers behave strangely with gimp. by default, gimp perl modules doesn't export functions, which makes perl programmers became fool ... I don't understand this patch nor the explanation you give.

Re: [Gimp-developer] [PATCH] mandrake patches dump

2002-06-12 Thread Thierry Vignaud
Sven Neumann [EMAIL PROTECTED] writes: well, my position in this thread is a bit biased since me and other GIMP developers have spent lots of their free time hunting down bugs that turned out to be caused by buggy GTK+ themes Mandrake used to ship. which ones ? i've only got bug reports

Re: [Gimp-developer] [PATCH] mandrake patches dump

2002-06-13 Thread Thierry Vignaud
Raphaël Quinet [EMAIL PROTECTED] writes: The details are in http://bugzilla.gnome.org/show_bug.cgi?id=55735 This has been fixed in Mandrake 8.0 one year ago, but we still got a duplicate bug report related to it this year. And it took a while for us to figure out that these apparently

Re: [Gimp-developer] Gimp binary size

2003-01-28 Thread Thierry Vignaud
Michael Natterer [EMAIL PROTECTED] writes: Yes, that's exactly the reason for the insane size. You probably use gcc 3.2?? I noticed the same some days ago. this is not related to the gcc version but to the default cflags. as for now, most packages come with -g or -g -O2 as default cflags due

Re: [Gimp-developer] gimp-perl-cvs status

2003-07-23 Thread Thierry Vignaud
[EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) writes: is it worth building the gimp-perl module from cvs yet? Depends on what you are needing it for. The evrsion in CVS seems to be fully working, except that none of the examples that use their own Gtk+ interface have been converted to gtk2

Re: [Gimp-developer] Third big serious meeting from GIMPcon

2003-08-22 Thread Thierry Vignaud
Dave Neary [EMAIL PROTECTED] writes: Another reason may be that it is difficult to build the development version because it depends on released versions of some libraries that are not included yet in the major GNU/Linux distributions (e.g., GTK+ version 2.2.2). both debian unstable, mandrake

Re: [Gimp-developer] Third big serious meeting from GIMPcon

2003-08-24 Thread Thierry Vignaud
Raphaël Quinet [EMAIL PROTECTED] writes: Another reason may be that it is difficult to build the development version because it depends on released versions of some libraries that are not included yet in the major GNU/Linux distributions (e.g., GTK+ version 2.2.2). both debian

Re: [Gimp-developer] Third big serious meeting from GIMPcon

2003-08-24 Thread Thierry Vignaud
Sven Neumann [EMAIL PROTECTED] writes: and anyway, maybe adding a few ifdef round gimp code using specific 2.2.x features if it can safely be disabled may help users of older releases or other distros. We did that for a while. It not only became difficult to maintain but at some point

[Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2

2003-12-01 Thread Thierry Vignaud
Sven Neumann [EMAIL PROTECTED] writes: While GIMP is approaching the 2.0 release, the libgimp* APIs are stabilizing and it's about time to update plug-ins so they will work with GIMP-2.0 as gimp packager in mandrake linux distribution, there's one thing that has always annoy me with the way

[Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2

2003-12-02 Thread Thierry Vignaud
Sven Neumann [EMAIL PROTECTED] writes: We do follow the standard library version numbering. The problem is that either you did not understand it or didn't look close enough. Let's have a look at configure.in: standard libray versioning scheme is to set soname to libname.major (library being

[Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2

2003-12-04 Thread Thierry Vignaud
Carol Spears [EMAIL PROTECTED] writes: [1] i provide gimp1.3 in contribs because so much people complain to me about font issues with gimp-1.2.x you could include the gimp-freetype plug-in (http://freetype.gimp.org) get the one with a 2 in it for gimp-1.2. this plug-in takes care of

Re: [Gimp-developer] Re: [Gimp-announce] ANNOUNCE: gimp-plugin-template 1.3.2

2003-12-05 Thread Thierry Vignaud
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

Re: [Gimp-developer] gimp2-freetype

2003-12-05 Thread Thierry Vignaud
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

Re: [Gimp-developer] gimp2-freetype

2003-12-05 Thread Thierry Vignaud
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