<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 16: Missing libtool libversion flag bump for new APIs</title><link>https://sourceforge.net/p/libmms/bugs/16/</link><description>Recent changes to 16: Missing libtool libversion flag bump for new APIs</description><atom:link href="https://sourceforge.net/p/libmms/bugs/16/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 18 Feb 2014 06:49:32 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/libmms/bugs/16/feed.rss" rel="self" type="application/rss+xml"/><item><title>Missing libtool libversion flag bump for new APIs</title><link>https://sourceforge.net/p/libmms/bugs/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Going from libmms 0.5 to 0.6.2, I see several new functions added to the public .h (and nothing removed or altered...thanks for retaining backward-compatibility!). Libtool's -version-info flag is intended to signal what (if any) types of interface changes are made (it's a library/interface versioning value, independent of the source version/release), but 0.6.2 has the same -version-info 0:2:0 (in src/Makefile.am libmms_LA_LDFLAGS) as 0.5 (signifying &lt;em&gt;no change&lt;/em&gt; to the interface). This versioning is important for downstream packagers and end-users so that they don't as easily downgrade their library and break things built against the newer version.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Macks</dc:creator><pubDate>Tue, 18 Feb 2014 06:49:32 -0000</pubDate><guid>https://sourceforge.net8ae5bc2cbe9c72c7497c0f935d4c14897eb6364a</guid></item></channel></rss>