Hi Jeremy, I think that is reasonable. Is there any point patching it for qt5 support if there's no qt5 in debian?
It sounds like the Ubuntu package will have to diverge here, for the moment. -Pete On Wed, Jun 26, 2013 at 9:59 AM, Jeremy Lainé <jeremy.la...@m4x.org> wrote: > Pete, > > Le Jun 26, 2013 à 10:55 AM, Pete Woods a écrit : > > > That macro is confusing, I admit. It actually enables the deprecated > functions! > > > > As Qt5 has not landed yet in Debian/unstable, I will be uploading QDjango > 0.3.0 without the Qt5 patch. > > As I'm also the upstream author, I will address any Qt5-related issues > upstream. I am a bit surprised by the need for the macro you mention, I had > successfully built QDjango against Qt5 betas. > > Does this sound OK to you? > > Jeremy
