Date: Thu, 4 Dec 2025 08:34:18 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD-pkgbase@freebsd.org, Colin Percival <cperciva@freebsd.org>, Lexi Winter <ivy@freebsd.org> Subject: armv7 context: with port-packages builds suspended, freshports indicates pkg versions 2.3.1, 2.2.2 (mostly), or "-": pkgbase use consequences? Message-ID: <856B6B71-B2C6-4A04-8903-B29B37AB6274@yahoo.com> References: <856B6B71-B2C6-4A04-8903-B29B37AB6274.ref@yahoo.com>
index | next in thread | previous in thread | raw e-mail
Note: General port-package builds being suspended makes sense to me for the resources available. I'm not suggesting for that to change. But pkg is rather special and became so for a wider range of usage with pkgbase. The details freshports reports for armv7 pkg versions: FreeBSD:16:latest : "-" FreeBSD:15:quarterly : "-" FreeBSD:15:latest : 2.2.2 FreeBSD:14:latest : 2.2.2 FreeBSD:14:quarterly : 2.2.2 FreeBSD:13:quarterly : 2.2.2 FreeBSD:13:latest : 2.3.1 Can there be a way (other than local port-package source builds) to have armv7 keep up with pkg updates for its pkgbase usage for armv7? If not, mentioning the requirement for armv7 pkg source based builds might cut down on support requests some. Note: The question is about general use, not mine: I already build my own port-packages (amd64, aarch64, armv7), including for pkg . Note: I've less context for them, but: FreeBSD:14:latest 1.19.1_1 : powerpc64le, 32-bit powerpc FreeBSD:14:quarterly 1.20.9 : powerpc64, powerpc64le, 32-bit powerpc FreeBSD:15:latest 1.20.9_1 : powerpc64, powerpc64le (n/a or "-" for the other powerpc* ABI combinations) The audience for powerpc* is likely rather different overall. === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?856B6B71-B2C6-4A04-8903-B29B37AB6274>