[mythtv] When will we deprecate Qt 5 and qmake/configure?

[jam at tigger.ws]

> >>> Has anything changed since the last time this was discussed? The 
> >>> problem
> >>> with removing support for configure/qmake is most if not all the
> >>> packages created for the various distros use it. Yes they can be 
> >>> updated
> >>> to use cmake but with Myth falling out of popularity a lot of the
> >>> packager maintainers no longer use MythTV themselves so are they going
> >>> to bother to update to cmake or just say sod it lets not bother? Could
> >>> be another nail in the coffin for the project?
> >
> > On the other hand, if we never say you should switch to CMake, no one 
> > will.
> >
> 
> Seriously why are you forcing everyone to use CMake! Why change it in 
> the first place? The project has been using configure/qmake since its 
> birth with no problems. It's mature, stable, works well and is well 
> documented and understood. It seems to be another of those things you 
> and David like to do that change something just for the sake of it with 
> little thought as to why you are making the change. What are the 
> benefits? How does this change affect other users like packagers for 
> example.
> 
> 
> For the record it's no secret I no longer use MythTV and don't count 
> myself as an active developer but I'd still hate for a silly decision 
> like this to add another blow to an already ailing project like MythTV.

Paul
I'm an auld fart with a serious if-it-aint-broke-don't-fixit attitude and a serious watch-and-learn philosophy.
cmake with some hand holdind from gemini turns out to be a very powerful tool !
EG I never bothered to learn about the daft python restrictions, but cmake delt with it cleanly
Resaying that with qmake I could not build and install mythtv, with cmake I could.

Because of that I started using cmake for my own projects eg using QT6, whisper.cpp on an iPad.
No doubt because of apple's insane (but actually clever) restrictions, cmake makes an awesome task easy.
James