> > However, for general-purpose systems like Unix, where the user is > > free to update its version of FreeType, or FTValid, it leads to the > > same problems that we encountered with Pango, fontconfig, etc.... > > Well, libtool's versioning scheme should prevent chaos. >
Excuse me for being explicit, but I'd rather poke my eyeballs with a rusty nail found in cow dung than believe this ! it also forces us to make all FT_BASE functions exported. > > but it would be a bad idea anyway. Really, the code in > ftvalid doesn't > > depend on FreeType anymore, I don't see why you'd want to introduce > > potential versioning problems on Unix by getting this dependency > > back. > > Code sharing. > As said previously, I believe that there are far too little benefits compared to far too much risks / versioning problems. > > What's so wrong with distinct libraries, really ? > > Nothing, but I would like to understand all implications since I've > never done such a thing before. Sorry for being obtrusive. > no, don't worry, it's OK :-) - David *********************************************************************************** Information contained in this email message is confidential and may be privileged, and is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the [EMAIL PROTECTED] and destroy the original message. *********************************************************************************** _______________________________________________ Freetype-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype-devel
