[discussion continued on freetype-devel only]
A new version which makes such a radical change should bump up the
shared object version (.so.N).
Where's the `radical change'?
That way we'll allow a transition period for applications to update.
This has been discussed recently on the
And will the major .so version be bumpped up?
Nope, because this would create problems as Owen Taylor pointed out,
since through indirect linking, a given program might find itself
dependent on both libfreetype6 and libfreetype7, which could cause
major problems depending on the code paths
I *think* fontconfig 2.3.93 doesn't use the internals
anymore... well, that's what the changelog for the release claims;
perhaps this could be noted on the patches page.
Added, thanks. Can someone verify this claim, please?
Werner
___
Werner LEMBERG wrote:
[discussion continued on freetype-devel only]
Sorry for that. I was to quick to press Send.
A new version which makes such a radical change should bump up the
shared object version (.so.N).
Where's the `radical change'?
Symbols which were previously
On Saturday 21 January 2006 14:06, Werner LEMBERG wrote:
I *think* fontconfig 2.3.93 doesn't use the internals
anymore... well, that's what the changelog for the release claims;
perhaps this could be noted on the patches page.
Added, thanks. Can someone verify this claim, please?
OK. I
OK. I bit the bullet and rebuild freetype and fontconfig... yes, it
does look like fontconfig-2.3.93 will compile against freetyle sans
internal headers.
Thanks a lot for the verification!
Werner
___
Freetype-devel mailing list
