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
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
On Tue, Dec 02, 2003 at 04:09:04PM +, Thierry Vignaud wrote:
[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
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
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
Hi,
Thierry Vignaud [EMAIL PROTECTED] writes:
but there's also the problem that currently we also have to rebuild
dependant packages on each gimp release because major bumped on each
release (since lib major equals version number's minor) even if there
really wasn't any api change.
i
Hi,
Thierry Vignaud [EMAIL PROTECTED] writes:
standard libray versioning scheme is to set soname to
libname.major (library being named libname.major.minor on
filesystem)
Don't get confused by the numbers, libgimp-2.0 is the library name
we've choosen. There is nothing wrong with that. It's
On Tue, Dec 02, 2003 at 04:09:04PM +, Thierry Vignaud wrote:
Sven Neumann [EMAIL PROTECTED] writes:
standard libray versioning scheme is to set soname to
libname.major (library being named libname.major.minor
on filesystem)
Don't get confused by the numbers, libgimp-2.0 is the
On Tue, Dec 02, 2003 at 11:30:26PM +0100, Marc A. Lehmann wrote:
On Tue, Dec 02, 2003 at 01:25:24PM -0800, Manish Singh [EMAIL PROTECTED] wrote:
since the major is not anymore unique (eg gimp-2.0.23 will provide
libgimp-2.0.so.23 with the same major as libgimp-1.3.so.23 from
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
Hi,
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:
#
# Making releases:
# GIMP_MICRO_VERSION += 1;
# GIMP_INTERFACE_AGE += 1;
# GIMP_BINARY_AGE += 1;
# if any
11 matches
Mail list logo
