https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285503
--- Comment #3 from Jason E. Hale <jh...@freebsd.org> --- (In reply to Peter TKATCHENKO from comment #2) > The history of private API is really strange, the last time I had problems > with VLC and dsbmc, I'm really surprised that they use private API. At a quick glance, I can't find any private Qt headers (grepping source for any _p.h) currently being used in VLC nor in DSBMC. Perhaps they were at some point, but digging through their history is more than I'm willing to do for the sake of this conversation. I don't know anything about DSBMC, but VLC is very popular and I don't recall any recent problems (I did the last update for that back in June). The usage of the Qt private API still persists in Qt6 projects, though, and I have to deal with those too. > IMHO, there are many many projects that cannot migrate to qt6. I hope, KDE > will continue to maintain qt5, otherwise we'll loose many software... No hard deadline has yet been set for Qt5 expiration, but hey python27 expired over 4 years ago and it's still with us. Seriously, though, if your favorite Qt5 app hasn't been ported to Qt6 yet, bug the maintainer of the project (not the maintainer of the port). Dead projects are going to be trimmed like the were for Qt3 and Qt4. I still have a Qt4 app that I miss, but it's gone and I moved on. Obviously, we're going to wait for very popular projects like VLC and Chromium, but more obscure projects are going to get steamrolled in no uncertain terms. It's irresponsible to keep potentially vulnerable software available for general consumption any longer than it has to be. -- You are receiving this mail because: You are the assignee for the bug.
