I've got a version of freetype2/freetype2-hinting 2.1.9 in my
experimental tree that, in theory, fixes issues of binary compatibility
and building by older packages. It includes some patches from debian
for backwards-compat as well as removing the error about including
ft2build.h first.
I would a
Hi Benjamin,
I still get with mozilla :
nsFreeType.cpp
g++-3.3 -I/sw/lib/freetype2/include
-I/sw/lib/freetype2/include/freetype2 -o nsFreeType.o -c
-DOSTYPE=\"Darwin7.8.0\" -DOSARCH=\"Darwin\" -I../..
-I../../../dist/include/xpcom -I../../../dist/include/string
-I../../../dist/include/pref -I..
On 27 Feb 2005, at 02:10, jfm wrote:
and I think 2.1.3 -> 2.1.4 is OK with any fink pkg
That was : 2.1.3 -> 2.1.7 ...
Jf
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
jfm wrote:
[]
The original purpose is still stated in DescDetail as :
"The freetype2 packages now exist only for compatibility with older Fink
packages. Developers should use the freetype that is part of XFree86
for new packages."
This formulation comes from a time when there was no xfree86-4.0 an
Martin Costabel wrote:
> My personal option for a solution would be to
This all sounds good to me.
Do you want to put the packages together, or should I get hacking on it?
---
SF email is sponsored by - The IT Product Guide
Read honest & cand
On Feb 27, 2005, at 9:45 AM, Martin Costabel wrote:
This formulation comes from a time when there was no xfree86-4.0 and
especially no xorg package yet. Right now we have no unique "freetype
that is part of XFree86". We are forced to live with several different
not really compatible freetype2 ve
Matthias Neeracher wrote:
[]
- Often there will be two different freetype.6.dylibs loaded into
memory at the same time, because X11's libfreetype will inevitably pop
up in addition to ours.
This inevitability seems to be an issue for me. Specifically, in
lilypond, I saw major breakage if I just
Benjamin Reed wrote:
Martin Costabel wrote:
My personal option for a solution would be to
This all sounds good to me.
Do you want to put the packages together, or should I get hacking on it?
I guess I can do it if you didn't already. I'll run a couple of builds
to be sure.
--
Martin
--
On 27 Feb 2005, at 18:45, Martin Costabel wrote:
My personal option for a solution would be to
- first upgrade the current freetype2 package to 2.1.4. This is
trivial to do. And to
- have an additional freetype219 package that installs everything
(including all its library files) into %p/lib/free
Jean-François Mertens wrote:
[]
Sounds perfect _ but are you sure you want 2.1.4 ?
I was just treading carefully here. It is perhaps true that 2.1.7
belongs rather to the 2.1.3 group than to 2.1.9, apart from the
artificial incompatibility in the freetype.h header. If we confirm this
with more c
On 28 Feb 2005, at 00:27, Jean-François Mertens wrote:
I see only the following pkgs in 10.3/unstable that depend on
freetype2 :
mozilla peacock ghex paragui pong gnome-pim autotrace scribus xdvik
transcode mlterm
Just recompiling them on an old panther machine to be sure .
Was too late yeste
11 matches
Mail list logo
