Update from qt5 to qt6

i've added mark's ZFS change and also documented this for the dist set path, as it's not pkgbase specific. i've added a new step for pkgbase to update the installed system, since we want users to be in the habit of doing this.

rf

Terriffic. Thanks! (with ports-secteam@ hat) that for some reason doesn't show in Phab.

In D57242#1317770, @bz wrote:

This isn't quite correct yet (though probably not wrong).

mt7921 has an entry for a different vendor as well these days:

{ PCI_DEVICE(PCI_VENDOR_ID_ITTIM, 0x7922),
        .driver_data = (kernel_ulong_t)MT7922_FIRMWARE_WM },

Not sure anymore if the script doesn't check or if it simply didn't barf and it goes unnoticed as it is the same device ID as for mediatek?

Another reason we need a newer fwget (I should get back and rewrite my lua take I) to avoid adding different files for vendors but rather have the logical unit be a driver or similar. *sigh*

I would suggest, for now, to manually add the extra file to fwget and not try to automate this just yet. Maybe a printf saying to check for other vendor IDs in the driver or to list them at the end?

grep -r PCI_VENDOR_ID sys/contrib/dev/mediatek/mt76/ | grep -v PCI_VENDOR_ID_MEDIATEK
sys/contrib/dev/mediatek/mt76/mt7921/pci.c:     { PCI_DEVICE(PCI_VENDOR_ID_ITTIM, 0x7922),

Ah, you haven't gone through and marked them as "done".

In D57628#1321586, @khorben wrote:

In D57628#1321573, @markj wrote:

How does one verify that a given executable is compiled with FORTIFY_SOURCE > 0?

AFAICT it works best when combined with -fstack-protector, and it depends on each and every libc call performed by the executable.

I just had a look at a simple program calling gethostname() (on amd64), and it injects a test right before the call.
The magic happens in /usr/include/ssp/*.h.

In D57628#1321573, @markj wrote:

How does one verify that a given executable is compiled with FORTIFY_SOURCE > 0?

rf

In D50958#1321407, @adrian wrote:

please address lwhsu's comments!

How does one verify that a given executable is compiled with FORTIFY_SOURCE > 0?

In D50958#1321108, @adrian wrote:

hi! this doesn't have a commit message in the description; would you please update that? thanks!

In D57610#1321422, @d.stoye_cms.hu-berlin.de wrote:

Or is it a blocker?

@ivy Can you add the tweaks from ziaee/markj and commit this? I don't think we need to add the "how to upgrade from 14.4 pkgbase" instructions; that's an unsupported path and would bloat the document too much (and risk confusing users).

In D56835#1321082, @vsasjason_gmail.com wrote:

Will it help sshd to start without being indefinitely blocked by e.g. mysqld? That would be enough of a reason for me personally to switch to this thing immediately.

Looks good to me. Many thanks for working on this!

Address review issues

In D57610#1321069, @makc wrote:

In D57610#1321024, @michaelo wrote:

GUI does not configure for me, qmake is missing:

not qmake, but webengine (USE_QT= webengine). Please, consider switching the port to Qt 6, since Qt 5 is EOLed. You may need to use CMAKE_ARGS= -DQT_VERSION_MAJOR=6 for that.

Make Q/A is unsure: