[sword-devel] Ubuntu 12.04 ....

[Troy A. Griffitts]

Awesome.  So it is as I suggested.  A user who downloads and builds 
Bibletime, not in debug mode, wouldn't see the error, and they would be 
able to upgrade their SWORD library without running into the problem? 
Cooleo.  Thanks for the details.

On 04/23/2012 04:35 PM, Greg Hellings wrote:
>> From the CMakeLists.txt file:
>
>      SET(CMAKE_CXX_FLAGS_RELEASE "-Wall -O2 -fexceptions")
>      SET(CMAKE_CXX_FLAGS_DEBUG   "-Wall -Werror -O2 -ggdb -fexceptions")
>
> It is the -Werror switch, only enabled in Debug builds, that causes
> the deprecation warnings to be show stoppers. Last I checked Debian
> demands to build with "-Wall -Werror" and debugging flags (Dmitriijs
> has thrown The Debian Book at me several times for circumventing that
> build policy in my CMakeLists.txt files; apparently Debian knows
> better than its application and library developers what flags its
> applications and libraries need when building) and will strip out
> debugging post-build. So the problem isn't actually BibleTime's but
> Debian's.
>
> Also, because us developers (almost) always build Debug, we don't
> build against SWORD SVN and haven't vetted against it as well as we
> would like so we don't encourage building BT against SVN. I only ever
> build against SVN and haven't noticed a problem, but we still don't
> encourage it.
>
> --Greg
>
> On Mon, Apr 23, 2012 at 8:46 AM, Troy A. Griffitts<scribe at crosswire.org>  wrote:
>> Not disputing the long term desire to not build against deprecated API
>> methods (that's why we deprecate), and I certainly understand the policy to
>> not release Bibletime until it is not using any deprecated methods of the
>> most recent SWORD library, but I can't see how it is useful to cause
>> Bibletime to fail building for an end user once it is released.
>>
>> If
>> Bibletime x.y.z is released which enforces this policy against
>> SWORD a.b.c and we subsequently release
>> SWORD a.b.d which is binary compatible with a.b but which adds deprecation
>> notices to additional method, then Bibletime x.y is violating the policy and
>> won't build for any user who simply wants to upgrade their SWORD engine.
>>
>> Could the check be added as a developer build option, so you can still
>> enforce it inhouse, but it wouldn't be forced on the end users?
>>
>> Just a thought.
>>
>> Troy
>>
>>
>>
>>
>> On 04/23/2012 03:14 PM, Greg Hellings wrote:
>>>
>>> On Mon, Apr 23, 2012 at 8:07 AM, Troy A. Griffitts<scribe at crosswire.org>
>>>   wrote:
>>>>
>>>> Not disputing any of this, but I'm curious why BT can't compile against
>>>> SVN.
>>>>   I don't believe we've intentionally made any API interface changes in a
>>>> while, and we try our hardest to be backward compatible.  If you let me
>>>> know, I can have a look at what we broke.
>>>>
>>>
>>> BibleTime will not compile against a deprecated API and there is one
>>> place where you've deprecated a method in favor of its new camel-cased
>>> version. We maintain a git branch with the necessary updates, but we
>>> don't want to release that branch as it would break compat with the
>>> current released SWORD (which is what we package on Windows and Mac).
>>>
>>> The refusal to build against deprecated APIs is a policy choice
>>> selected by Jaak which the rest of the developers agreed was
>>> desirable.
>>>
>>> --Greg
>>>
>>>> Troy
>>>>
>>>>
>>>> On 04/23/2012 02:49 PM, Greg Hellings wrote:
>>>>>
>>>>>
>>>>> Xiphos 3.1.5 requires SWORD SVN. In the Crosswire Ubuntu PPA current
>>>>> SVN of SWORD is named libsword9.
>>>>>
>>>>> BibleTime 2.9.1 cannot be built against SWORD SVN but only against
>>>>> SWORD 1.6.2. In Ubuntu's current release this version of SWORD is
>>>>> named libsword8.
>>>>>
>>>>> There is a branch in BibleTime's git repository which allows it to be
>>>>> built against SWORD's SVN, but because of API changes since then our
>>>>> current trunk cannot be built. BibleTime will not release a version
>>>>> which is incompatible with the current SWORD release and that is why
>>>>> we requested that Troy cut a new release of SWORD. Once SWORD 1.7
>>>>> (libsword9 in Ubuntu/Debian parlance) is released the next version of
>>>>> BibleTime released after that will be compatible with the new API and
>>>>> will therefore require libsword9.
>>>>>
>>>>> If you want to get more to the bottom of it, try providing Dmitrijs
>>>>> with the information he specified, but it sounds like you are drawing
>>>>> the official Ubuntu package of BibleTime and the PPA package of Xiphos
>>>>> to get the conflict you indicated.
>>>>>
>>>>> --Greg
>>>>>
>>>>> On Mon, Apr 23, 2012 at 6:40 AM, Barry Drake<bdrake at crosswire.org>
>>>>>   wrote:
>>>>>>
>>>>>>
>>>>>> On 23/04/12 12:11, Dmitrijs Ledkovs wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> do not mix PPAs with official archive.
>>>>>>>
>>>>>>
>>>>>> I understand that.  What I'm doing is reporting that there is a problem
>>>>>> in
>>>>>> the packages held in Ubuntu 12.04 repo.  I'm asking whoever is
>>>>>> responsible
>>>>>> for submissions to Ubuntu to get things up to date as soon as possible.
>>>>>>   I
>>>>>> know the official packages are OK but 12.04 is released on Thursday of
>>>>>> this
>>>>>> week so I'm doing some final testing!  The new user of 12.04 is NOT
>>>>>> going
>>>>>> to
>>>>>> look for the official ppa but will simply use Ubuntu Software Centre -
>>>>>> and
>>>>>> get the conflict.
>>>>>>
>>>>>> God bless,        Barry.
>>>>>>
>>>>>> --
>>>>>> Barry Drake is a member of the the Ubuntu Advertising team.
>>>>>> http://ubuntuadverts.org/
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>>> Instructions to unsubscribe/change your settings at above page
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>> Instructions to unsubscribe/change your settings at above page
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> Instructions to unsubscribe/change your settings at above page
>>>
>>>
>>> _______________________________________________
>>> sword-devel mailing list: sword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page