@DiapDealer,
Quote:
Originally Posted by DiapDealer
I don't believe I'd worry about making any more invasive changes to another Qt5 source release. For the few people it might impact, the recommendation would be to upgrade to a version based on the first Qt6-only source release.
|
Okay, I brought all of our late 2.2.0 and 2.2.1 changes over from master, pulled in the qt6only changes from my repo, and then added in a bunch of force nfc changes.
So this is a bleeding edge tree that will need some heavy testing.
I pushed it to my personal github repo in the qt6only branch.
git clone
https://github.com/kevinhendricks/Sigil.git
cd Sigil
git checkout qt6only
If you agree, I would like to create a "qt5final" branch from current master to preserve it for any Linux distributions that are too old for Qt 6.2.X or 6.4.X. If we find that all the force nfc stuff is solid, we can even add to that branch and make a new qt5final update release. But I want to make sure the nfc force stuff is rock solid first.
Once we have that, I will merge in my "qt6only" branch into Sigil-Ebook master in the form of sets of patches so that we do not lose any history of what has been done and can revert them in pieces if necessary. Something along the lines of:
1. remove old qt5 support cleanup patch
2. remove need for Qt6 compat5 (no qstringref patch, no qtextcodec patch)
3. force nfc patches
Just let me know when you want me to start the transition.