Bug#704044: ogre-1.8: Please upgrade ogre to 1.8.1 for boost1.53 transition (jessie)

[Manuel A. Fernandez Montecelo]

2013/5/21 Dmitrijs Ledkovs <xnox at debian.org>:
>> Upgrading OGRE to 1.8.1 would maybe require to change the SOVERSION
>> and binary package name, having to go through ftp-new queue.  1.9-rc1
>> is already out, I think that it would be better to go with this one.
>
> Any ETA on the final? Or your personal guess from experience?

They've been slow in the past, but new people took over (or more
relevant roles recently) and they address things differently, and do
nice things like supporting co-installability of different versions
(the Debian package already managed to work around limitations) and
removing embedded libraries from the code.

RC1 has been out for just over a month now, I asked on IRC but didn't
get a reply.  My guess is that between 1 and 4 months from now.


>> I think that from your boost-transition POV, until all OGRE and their
>> dependencies are removed, you cannot get rid of 1.49.  But if you only
>> want to move boost-defaults from 1.49 to 1.53 [1], all these packages
>> are not a problem -- we depend specifically on 1.49, for the reasons
>> stated in my first reply to this bug report.
>
> Correct. My end goal is to remove 1.49 though =) not just flip the
> default over ;-)

I understand that you will get rid of it and if possible not shipped
in next stable; but in the meantime I was asking for clarification if
OGRE was really interfering-with/holding-up this transition, or if
there's a reason to hurry things up.

Unless there's a very compelling reason, I will try to have only
packages for 1.9 or newer ones for next stable, none of them will
depend on boost 1.49.


>> So if you change libboost-thread-dev to point to
>> libboost-thread1.53-dev from 1.49, none of these packages (ogre and
>> packages using it) will be affected.  Is this correct, or I am missing
>> something?  Did OGRE packages fail to build in hist tests of #704032?
>
> Sure. It's just current versions of ogre do not build against 1.53,
> and i'd rather would like to keep on top of "things that need to
> happen to remove boost1.49".
>
> Please keep this bug open until you build against newer boost 1.53 or better.

Will do.


Cheers.