Re: Bug#316031: libfreetype6: API changes from 2.1.7 to 2.1.10
> On Mon, Jun 27, 2005 at 10:29:55PM -0500, Ming Hua wrote:
> > So from my understanding, it's urgent for libfreetype6 to bump its
> > shlibs from "libfreetype6 (>= 2.1.5-1)" to "libfreetype6 (>=
> > 2.1.10-1)".
On Mon, Jun 27, 2005 at 10:14:32PM -0700, Steve Langasek wrote:
> No. See bug #314385: this library package's *name* needs to change,
> because of the issue you describe below.
Sorry, I somehow missed your comments in bug #314385. So does this mean
that upstream should have increased their SONAME on 2.1.10?
On Tue, Jun 28, 2005 at 10:53:45AM +0100, Will Newton wrote:
> I think the best thing to do is add a freetype2.1.7 source package
> that builds libfreetype6 with an epoch and coordinate with upstream
> the change to the soname - the next release looks like it is meant to
> break the ABI (more than normal that is).
> Does that sound reasonable? I'd rather not epoch the package but I
> don't see any other choice here.
I must admit I am quite ignorant on library packaging, but is ``upload a
freetype-2.1.7 source package which only build libfreetype6 with old
API, then upload freetype source package which build everything and
change the shared library binary package to something like
libfreetype6a with new API, and finally rebuild all package that depend
on libfreetype6 and was uploaded after 2.1.10-1 upload'' an option?