Well, that is inspirational enough - let's be the first to do historical versioning instead of slapping a single version on each symbol with each iteration of the API.
I mean, I am willing to do the work, so I am guessing your hesitance is more based on the principle of the matter, not the additional work it would take (since I am going to do it). On Tue, Jan 30, 2018 at 4:40 PM, Alexei Podtelezhnikov <apodt...@gmail.com> wrote: > > > On Tue, Jan 30, 2018 at 3:30 PM, Behdad Esfahbod <beh...@cs.toronto.edu> > wrote: > >> I want to hear from downstreams that want to add symbol-versioning to >> FreeType first, why do they need to. >> > > I need some inspiration, some good examples to follow. Besides glibc, so > far I've only seen silly wrappers that slap a single version on all symbols > regardless of history. >
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
