[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: libprojectM, new upstream version.


On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> Hi,
> I've packaged the new version of this library, the upstream author has
> changed the SONAME, and so I've changed the name of the lib and -data
> package, not changed the name of the -dev file because the old
> maintainer has chosen to not version the package.
> This is my first library package, and I've some doubts, is for this that
> I'm asking for RFC...
> Is it correct to replace the old library? This can cause some breakage
> with old linked binaries (if any, I've seen that no package depends on
> this library)...


You will have to at least update audacious-plugins to work before doing

> about the change of SONAME by the upstream author, is it correct to
> change the SONAME if the library is compatible with the old one?

The library isn't compatible. Upstream breaks the API with every
release, so I gave up on them.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: