checking external lib versions (was: libreoffice + liborcus build problem)

2013-05-21 Thread Bjoern Michaelsen
Hi,

On Sat, May 18, 2013 at 05:40:38PM -0400, Kohei Yoshida wrote:
 
 Trying to build libreoffice 4.0.3.3 with liborcus 0.5.1 and that
 unfortunately
 fails with:
 You can't build the 4.0 branch with 0.5.1. You need to use 0.3.0.

As package maintainer, I have been repeatedly nagged about the versioning of
the essentially TDF-hosted but officially external libs (not only orcus, but
also wp*, cmis and friends). Proper versioning would go with full so-name
versioning for ABI-changes etc. AFAIK Rene is retrofitting this somewhat on the
Debian packages, but it would be better if this would happen directly upstream.
If we dont want to do that work, wouldnt it make sense though to at least
detect the version in the configure-script to safe newcomers frustrations?
Might be an EasyHack, if the supported versions of these external libs are
clearly defined.

Best,

Bjoern
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: checking external lib versions

2013-05-21 Thread Kohei Yoshida

On 05/21/2013 08:10 AM, Bjoern Michaelsen wrote:

Hi,

On Sat, May 18, 2013 at 05:40:38PM -0400, Kohei Yoshida wrote:

Trying to build libreoffice 4.0.3.3 with liborcus 0.5.1 and that
unfortunately
fails with:

You can't build the 4.0 branch with 0.5.1. You need to use 0.3.0.

As package maintainer, I have been repeatedly nagged about the versioning of
the essentially TDF-hosted but officially external libs (not only orcus, but
also wp*, cmis and friends). Proper versioning would go with full so-name
versioning for ABI-changes etc.
FWIW, liborcus clearly defines API version.  The one for 4.0 is 
liborcus-4.0, and the one for the master is liborcus-6.0. Is there 
anything else you are suggesting we do?



  AFAIK Rene is retrofitting this somewhat on the
Debian packages, but it would be better if this would happen directly upstream.
If we dont want to do that work, wouldnt it make sense though to at least
detect the version in the configure-script to safe newcomers frustrations?

Sure. That would be a great idea.  I have no objection.

Kohei

--
Kohei Yoshida, LibreOffice Calc hacker, SUSE.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: checking external lib versions

2013-05-21 Thread Kohei Yoshida

On 05/21/2013 08:16 AM, Kohei Yoshida wrote:
FWIW, liborcus clearly defines API version.  The one for 4.0 is 
liborcus-4.0, and the one for the master is liborcus-6.0.

I meant orcus-0.4 and orcus-0.6, respectively.

--
Kohei Yoshida, LibreOffice Calc hacker, SUSE.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: checking external lib versions

2013-05-21 Thread Bjoern Michaelsen
On Tue, May 21, 2013 at 08:16:44AM -0400, Kohei Yoshida wrote:
 On 05/21/2013 08:10 AM, Bjoern Michaelsen wrote:
 Hi,
 
 On Sat, May 18, 2013 at 05:40:38PM -0400, Kohei Yoshida wrote:
 Trying to build libreoffice 4.0.3.3 with liborcus 0.5.1 and that
 unfortunately
 fails with:
 You can't build the 4.0 branch with 0.5.1. You need to use 0.3.0.
 As package maintainer, I have been repeatedly nagged about the versioning of
 the essentially TDF-hosted but officially external libs (not only orcus, but
 also wp*, cmis and friends). Proper versioning would go with full so-name
 versioning for ABI-changes etc.
 FWIW, liborcus clearly defines API version.  The one for 4.0 is
 liborcus-4.0, and the one for the master is liborcus-6.0. Is there
 anything else you are suggesting we do?

Hmm, indeed:
$ readelf -d /usr/lib/liborcus-0.4.so.0|grep soname
 0x000e (SONAME) Library soname: [liborcus-0.4.so.0]

I need to check which libs that nagging was about.

Best,

Bjoern
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice