Date: Mon, 29 Dec 2025 15:23:30 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 292017] emulators/wine-proton: No supported path for i386 packages on 15.x breaks pkg32 compatibility Message-ID: <bug-292017-32340-cuiOSlMEdy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-292017-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-292017-32340@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292017 --- Comment #2 from Generic Rikka <rikka.goering@outlook.de> --- Thanks for the clarification — that makes sense: “32-bit binary execution remains expected” meaning a supported 14.x/13.5 i386 world can still run on the 15.x amd64 kernel via chroot/jail. My concern is the desktop/gaming usability impact: for common Wine/Proton/Steam workflows on amd64, users need a straightforward way to obtain and maintain the 32-bit ports userland. Requiring a separate i386 chroot/jail (and managing packages inside it) is significantly more complex than the previous pkg32-style workflow and is a major barrier for everyday users who “just want games to run.” Could we document an official, supported recipe for this use case (Wine/Proton needing 32-bit libs), and clarify whether an official package feed for “i386 ports userland for amd64 compat” is intentionally out of scope for 15.x? If it is out of scope, explicit documentation (and potentially guidance/deprecation notes for pkg32 workflows on 15.x) would help set expectations. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-292017-32340-cuiOSlMEdy>