UPDATE: veusz-4.2

Simple switch from Qt5 to Qt6 update veusz-4.2. Tested on amd64. OK?

Cheers Rafael

diff --git a/math/veusz/Makefile b/math/veusz/Makefile
index 01dc8b1a323..0aa91f05191 100644
--- a/math/veusz/Makefile
+++ b/math/veusz/Makefile
@@ -1,30 +1,30 @@
COMMENT = scientific plotting and graphing package
-MODPY_DISTV = 3.6.2
+MODPY_DISTV = 4.2
DISTNAME = veusz-${MODPY_DISTV}
CATEGORIES = math graphics
-REVISION = 6

HOMEPAGE = https://veusz.github.io/

# GPLv2+
PERMIT_PACKAGE = Yes

-WANTLIB += ${COMPILER_LIBCXX} Qt5Core Qt5Gui Qt5Widgets Qt5Xml
+WANTLIB += ${COMPILER_LIBCXX} Qt6Core Qt6Gui Qt6Widgets Qt6Xml
WANTLIB += m

SITES = https://github.com/veusz/veusz/releases/download/${DISTNAME}/

MODULES = lang/python \
- x11/qt5
+ x11/qt6
MODPY_PYBUILD = setuptools

BUILD_DEPENDS = devel/py-sip \
math/py-numpy \
textproc/py-tomli \
- x11/py-qt5
+ x11/py-qt6

RUN_DEPENDS = math/py-numpy \
- x11/py-qt5
+ x11/py-qt6
+
TEST_DEPENDS = ${BASE_PKGPATH}

do-test:
diff --git a/math/veusz/distinfo b/math/veusz/distinfo
index b5d7be65267..db88492e5c5 100644
--- a/math/veusz/distinfo
+++ b/math/veusz/distinfo
@@ -1,2 +1,2 @@
-SHA256 (veusz-3.6.2.tar.gz) = whcaxF5LMEJNj8NSYeLpnb5uJboRl+vCQ1WxBrJjldE=
-SIZE (veusz-3.6.2.tar.gz) = 3330225
+SHA256 (veusz-4.2.tar.gz) = jyghPk/u4THHnXrG/UDzHfW4AkS6n0CEd3VK+GX9he0=
+SIZE (veusz-4.2.tar.gz) = 3435250
diff --git a/math/veusz/pkg/PLIST b/math/veusz/pkg/PLIST
index 6fc82681017..83900059cff 100644
--- a/math/veusz/pkg/PLIST
+++ b/math/veusz/pkg/PLIST
@@ -357,8 +357,6 @@ lib/python${MODPY_VERSION}/site-packages/veusz/icons/button_ternary.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/button_vectorfield.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/button_volume3d.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/button_xy.svg
-lib/python${MODPY_VERSION}/site-packages/veusz/icons/downarrow.png
-lib/python${MODPY_VERSION}/site-packages/veusz/icons/downarrow_blank.png
lib/python${MODPY_VERSION}/site-packages/veusz/icons/error_bar.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/error_barbox.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/error_barcurve.svg
@@ -426,7 +424,6 @@ lib/python${MODPY_VERSION}/site-packages/veusz/icons/kde-zoom-out.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/kde-zoom-page-veuszedit.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/kde-zoom-veuszedit.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/kde-zoom-width-veuszedit.svg
-lib/python${MODPY_VERSION}/site-packages/veusz/icons/link.png
lib/python${MODPY_VERSION}/site-packages/veusz/icons/logo.png
lib/python${MODPY_VERSION}/site-packages/veusz/icons/logo.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/settings_axisgridlines.svg
@@ -458,6 +455,9 @@ lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-arrow-ew.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-arrow-nesw.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-arrow-ns.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-capture-data.svg
+lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-dropdown-blank.svg
+lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-dropdown-link.svg
+lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-dropdown.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-edit-custom.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-edit-cut.svg
lib/python${MODPY_VERSION}/site-packages/veusz/icons/veusz-edit-prefs.svg

Re: NEW: sysutils/starship

On 3/7/26 7:12 PM, Lydia Sobot wrote:
>> You'll need a WANTLIB line, and it would be nicer to use PORTHOME instead
>> of your custom TESTHOME. Creating .config under ${PORTHOME} makes a few more
>> tests pass for me, when testing with privsep enabled.
> Noted, I think I took the TESTHOME pattern from another port but I
> forgot where from,

A quick grep for TESTHOME indicates it might be the tcl/tk ports.

> but also if I may, what purpose does WANTLIB serve
> here?

man 7 library-specs

It serves the same purpose here as it does everywhere :-)

> In general actually I spent much more of my time trying to figure
> out how to make the ports framework cooperate with me adding crate
> dependencies with licences and all that rather than actually making the
> program compile

It gets easier once you committed the steps of updating a rust port to muscle
memory ;-)

Porting is arguably a bit more involved than just making stuff compile: After
all the whole point is to make it build and install for everyone, not just for
yourself.

Just remember:
https://www.openbsd.org/images/hackathons/p2k9.gif