linux-kernel - Qt6 port of kconfig qconf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <boris.20230717111132@codesynthesis.com>
Date:   Mon, 17 Jul 2023 11:27:16 +0200
From:   Boris Kolpackov <boris@...esynthesis.com>
To:     linux-kbuild@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Masahiro Yamada <masahiroy@...nel.org>
Subject: Qt6 port of kconfig qconf

Is there interest in the Qt6 port of qconf (which is currently Qt5)?

I took an exploratory stab at it and I've managed to make it compile
and run with relatively few changes, though there are quite a few
warnings about using deprecated stuff.

I can see three possible approaches here:

1. Drop Qt5 support and port qconf to be exclusively Qt6. This should
   allow cleaning up all the deprecated stuff.

2. Support Qt5 and Qt6 in the same qconf.cc. With this approach it's
   unlikely we will be able to cleanup the deprecated stuff without
   turning it into an #if soup.

3. Leave qconf.cc to be Qt5-only and make the changes in the qconf6.cc
   copy. This will allow us to clean up all the deprecated stuff but
   will require applying further changes to two files until we drop
   support for Qt5.

Thoughts?