In D52146#1191167, @kevans wrote:

e.g., routers, which likely don't want to drop some valuable storage on GCC. You'll note in the PR that they're just running py-duckdb, which has numpy as a dependency but doesn't really need BLAS.

This is not numpy's problem. I also commented in the PR but it bears repeating, anything built with GCC, including with gfortran in this case, needs the GCC libraries to operate properly. flang exists but I haven't had a chance to try building with it yet, but is part of the larger overhaul.

If you're toggling non-default options on a port like numpy, you really need to understand the consequences of it.

In the Python world, we cannot underestimate pilot errors. You need to consider the userbase of numpy, many of whom are not necessarily as versed in software like we are, and just see "ooh reduce dependency". Disabling fortran support is a pretty fatal one.

As for the proposed changes themselves, these will not apply after numpy is switched to building under PEP-517, amongst other things.

Can you suggest a better approach that would be compatible going forawrd? (When is the PEP-517 switch actually going to happen?)

It's been in my tree for quite some time, but simply missing some sanity checks.

It's unfortunate that we couldn't have gotten python@ feedback of this sort on this at any point in the last three years that the PR has been open- I guess we need more python@ staffing. =\

It's also unfortunate that the Python ecosystem overall has a very particular way of doing things and is a mess to even start learning.

Please elaborate further on "in some case this can be needed in some specifics environment to not have such dependencies." numpy isn't exactly meant to run on constricted environments, and fortran and BLAS support are generally considered fundamental components. Adding these options invites noise from those shooting themselves in the foot.

False alarm. Turns out pkgbase's plist logic relies on at least staging changes in git (no need to commit).

pkgbase fails:

===> Creating FreeBSD-kernel-malvern-15.snap20250627004823
rm -f /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src.plist 2>/dev/null || :
/usr/src/release/packages/generate-ucl.lua  PKGNAME "src"  PKGGENNAME "src"  VERSION "15.snap20250627004823"  DESC "FreeBSD Kernel Sources"  COMMENT "FreeBSD Userland Sources"  PKG_NAME_PREFIX "FreeBSD"  PKG_MAINTAINER "re@FreeBSD.org"  PKG_WWW "https://www.FreeBSD.org"  /usr/src/release/packages/template.ucl  /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src.ucl
pkg -o ABI=FreeBSD:15:amd64  -o OSVERSION="1500048"  create -f tzst -l -1  -M /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src.ucl  -p /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src.plist  -r /usr/src  -o /usr/home/vishwin/boards/malvern/obj/usr/src/repo/FreeBSD:15:amd64/15.snap20250627004823
rm -f /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src-sys.plist 2>/dev/null || :
/usr/src/release/packages/generate-ucl.lua  PKGNAME "src-sys"  PKGGENNAME "src"  VERSION "15.snap20250627004823"  DESC "FreeBSD Kernel Sources"  COMMENT "FreeBSD Kernel Sources"  PKG_NAME_PREFIX "FreeBSD"  PKG_MAINTAINER "re@FreeBSD.org"  PKG_WWW "https://www.FreeBSD.org"  /usr/src/release/packages/template.ucl  /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src-sys.ucl
pkg -o ABI=FreeBSD:15:amd64  -o OSVERSION="1500048"  create -f tzst -l -1  -M /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src-sys.ucl  -p /usr/home/vishwin/boards/malvern/obj/usr/src/amd64.amd64/sourcestage/src-sys.plist  -r /usr/src  -o /usr/home/vishwin/boards/malvern/obj/usr/src/repo/FreeBSD:15:amd64/15.snap20250627004823
pkg: Unable to access file /usr/src/sys/dev/sound/midi/sequencer.c:No such file or directory
pkg: Unable to access file /usr/src/sys/dev/sound/midi/sequencer.h:No such file or directory
*** Error code 1

rebase

• add missing patch to obviate port LLVM for JIT

Won't be able to test till I fully get home from the K-W Hackathon next week. Just want to make sure userspace sequencing via audio/alsa-seq-server or audio/sndio (what I use) are not affected.

• python.mk: introduce PYTHON_CEXT_SUFFIX

• fix packaging, again

• databases/py-{gdbm,sqlite3}, x11-toolkits/py-tkinter: use correct distfile for 3.13

• update to 3.13.5

I blame BSDCan for missing the build hook-up

• bsd.default-versions.mk: add Python 3.13t

• split off threaded/GIL-disabled configuration into a child port

• lang/python313: update to 3.13.4

This is a duplicate of D49680. There is still far too much work to do on this port alone.

• pull in upstream commit addressing CVE-2025-4516

• update to 80.9.0