Hi, I am not sure whether the following make sense for the dvbcut package, but what about the following?
I suppose that the future of dvbcut will be Qt4!? So what about creating a new Qt3 branch where you continue to maintain dvbcut for Qt3 and start passing trunk to Qt4. I am aware that it would represent more work to maintain two branches, but it has the advantage of not having to bury Qt3. Cheers, Francesco On 21/01/12 19:05, Michael Riepe wrote: > Hi. > > On 01/21/12 13:23, Reinhard Tartler wrote: > >> I see. What I understand is that the cmake build system is basically >> not blessed by upstream, and it was a mistake to settle on it in the >> debian package. Moreover, the qt4 patch in its current form only works >> with the cmake system. > > Well, what's "blessed," as you call it, is the Qt3/autoconf combination. > > Qt4/autoconf would be okay, too, as long as everybody is aware that > there's no way back once I incorporate the patch, and that the Qt3 > version is effectively dead and buried at the same time. > >> Therefore, you'd require the Qt4 port to work >> with the autoconf. > > It must also work on Windows/MinGW, as the Qt3 port does. Let's not > forget that there are more operating systems than just Linux and its > derivatives. > ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ DVBCUT-devel mailing list DVBCUT-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-devel
