Announcement

Collapse
No announcement yet.

Debian Buster Hopes To Drop Qt4

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Debian Buster Hopes To Drop Qt4

    Phoronix: Debian Buster Hopes To Drop Qt4

    Debian developers are still hoping they will be able to remove the Qt4 tool-kit during the Debian 10 "Buster" development cycle...

    http://www.phoronix.com/scan.php?pag...ts-To-Drop-Qt4

  • #2
    If they plan to get rid of OpenSSL 1.0, they better start shipping Qt 5.10 then because most of Qt5 has the same limitation since OpenSSL 1.0 and OpenSSL 1.1 are neither remotely binary nor source compatible, and you can only ever support one of them at a time. Debian really needs to ship both of them for some time more.

    Comment


    • #3
      Debinan 9 Stretch (current stable) has already switched to openssl 1.1 with no parallel 1.0 option.

      Comment


      • #4
        Never really understood how things like Qt4 somehow stay around. Did the API really change that drasticaly in Qt5 to make it a pain in the ass to port? I'd imagine for the majority of apps the migration should be relatively easy, unless you are doing some hardcore stuff.

        Comment


        • #5
          Originally posted by Trevelyan View Post
          Debinan 9 Stretch (current stable) has already switched to openssl 1.1 with no parallel 1.0 option.
          Bullshit.

          https://tracker.debian.org/pkg/openssl1.0

          Comment


          • #6
            Originally posted by cen1 View Post
            Never really understood how things like Qt4 somehow stay around. Did the API really change that drasticaly in Qt5 to make it a pain in the ass to port? I'd imagine for the majority of apps the migration should be relatively easy, unless you are doing some hardcore stuff.
            The Debian ftp-masters team usually doesn't (read: never) remove anything, even when requested to do so, as long as there are reverse dependencies that will be broken by this removal.

            For any popular library there are always a number of packages uploaded that are basically unmaintained. Someone keeps arguing they maintain it, but they don't do the porting work.

            Eventually, given long enough time, things are removed. It just takes a really long time.

            Getting things removed from the Debian archive is one of the hardest tasks you can imagine in debian development (unfortunately).

            Comment


            • #7
              Originally posted by cen1 View Post
              Never really understood how things like Qt4 somehow stay around. Did the API really change that drasticaly in Qt5 to make it a pain in the ass to port? I'd imagine for the majority of apps the migration should be relatively easy, unless you are doing some hardcore stuff.
              Some things are just not maintained or updated very often.

              Comment


              • #8
                Originally posted by cen1 View Post
                Never really understood how things like Qt4 somehow stay around. Did the API really change that drasticaly in Qt5 to make it a pain in the ass to port? I'd imagine for the majority of apps the migration should be relatively easy, unless you are doing some hardcore stuff.
                Well, KDE as we all know is based on Qt.
                When Plasma 5 came out, a lot of things had to be written again from scratch due to source incompatibility between Qt versions.
                Even now, porting KDE4/Qt4 programs to Qt5 is still underway in the KDE camp, it is at the point where as of next month, anything still using Qt4 is just going to be dropped from all KDE Applications, and Frameworks releases because of the huge effort required to create a functional port to Qt5.
                Now, that is not to say that what gets dropped now can not be added again in the future, AFTER it gets ported to Qt5.

                Comment


                • #9
                  Originally posted by mzs.112000 View Post

                  Well, KDE as we all know is based on Qt.
                  When Plasma 5 came out, a lot of things had to be written again from scratch due to source incompatibility between Qt versions.
                  Even now, porting KDE4/Qt4 programs to Qt5 is still underway in the KDE camp, it is at the point where as of next month, anything still using Qt4 is just going to be dropped from all KDE Applications, and Frameworks releases because of the huge effort required to create a functional port to Qt5.
                  Now, that is not to say that what gets dropped now can not be added again in the future, AFTER it gets ported to Qt5.
                  Well, KDE's problem was not moving from Qt4 to Qt5, that part was trivial, it was moving from kde4's kdelibs to kde5's kde-frameworks,

                  Comment

                  Working...
                  X