Quote:
Originally Posted by eschwartz
As it has been established that Sigil does not officially support 5.6.0 (because that would require building Qt5 from scratch to get QtWebKit), there is all of a sudden an unexpected chance that things will break and bleeding-edge distros have issues because we move so fast. 
But as you say -- hopefully nothing insurmountable. |
Well, in all fairness ... it has only been established that Sigil does not officially support the Nokia-provided pre-compiled Qt5.6 packages.
If, in a few years, when other distros get around to providing Qt5.6 (and prove to have with WebKit backported), I may lift my "unsupported" notice and change my build instructions to use the distro-provided Qt5 instead of Nokia's.
Fun stuff. Many distro's Qt5 packages are just now
becoming sufficient to build Sigil with (which is why Nokia's packages have been recommended in the first place), and Arch's Qt5 version may soon be too advanced to build Sigil. Damned if you do; damned if you don't. Never mind Windows developers who would love to be able to use Qt5.6 because of the great Qt5/ Python 3.5/Sigil/VS2015 convergence that may only happen once in our lifetimes (but can't because now that all pieces can use the same compiler runtime, Qt5 dropped a component Sigil relies on. Oh well. I'm used to building Qt on Window anyway).
