On Wed, Nov 21, 2012 at 12:58:34AM +0100, Jan Engelhardt wrote:
>
> On Tuesday 2012-11-20 20:59, Mikko Levonmaa wrote:
> >
> >What I was actually trying to propose in my previous mail is that
> >even when the current api version is 0 we could already have the
> >mechanics in place to increment the
On Tuesday 2012-11-20 20:59, Mikko Levonmaa wrote:
>
>What I was actually trying to propose in my previous mail is that
>even when the current api version is 0 we could already have the
>mechanics in place to increment the api version when the time comes,
>or is that automatically handled?
It is
On Tue, Nov 20, 2012 at 3:00 AM, Jan Engelhardt wrote:
> On Friday 2012-11-09 18:54, Mikko Levonmaa wrote:
>
>>Right, so if the first api version is 0 then it make sense, sort of,
>>matter of preference I guess. So, the original patch was wrong, however
>>the new suggestion was actually geared tow
On Friday 2012-11-09 18:54, Mikko Levonmaa wrote:
>Right, so if the first api version is 0 then it make sense, sort of,
>matter of preference I guess. So, the original patch was wrong, however
>the new suggestion was actually geared towards the future and the next
>release(s), so if I'm not mi
Right, so if the first api version is 0 then it make sense, sort of, matter
of preference I guess.
So, the original patch was wrong, however the new suggestion was actually
geared towards the future
and the next release(s), so if I'm not mistaken that needs to be done
through the -version-info and
Hi
On Fri, Nov 9, 2012 at 6:17 PM, Mikko Levonmaa wrote:
> Yes, true. Still to me having a meaningful version number in the actual
> library files does provide value.
>
> Also the manual does suggest that a -version-info is provided if we want to
> use libtool's versioning system,
> albeit they d
Yes, true. Still to me having a meaningful version number in the actual
library files does provide value.
Also the manual does suggest that a -version-info is provided if we want to
use libtool's versioning system,
albeit they discourage the direct relation to the actual package version
name.
htt
On Tue, Nov 06, 2012 at 03:57:47PM -0800, Mikko Levonmaa wrote:
> Adds the wayland version information to the shared libraries.
> libwayland-server.so.0.0.0 -> libwayland-server.so.1.0.0
The libtool versioning is different from the pacakge version number.
See:
http://www.gnu.org/software/libtool/
Adds the wayland version information to the shared libraries.
libwayland-server.so.0.0.0 -> libwayland-server.so.1.0.0
Signed-off-by: Mikko Levonmaa
---
src/Makefile.am |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/src/Makefile.am b/src/Makefile.am
index f93954e..0a79
