I’m trying to build this because it’s a requirement for www/otter-browser. The one from packages keeps segfaulting on me. However, looking at this port it seems that the project has been inactive since 2020, the latest updates to the port itself are from 2023 and it still uses qtwebengine for qt5, which is also from 2020, so probably not a good idea to use this browser anyways.
El El vie, 4 de jul de 2025 a la(s) 10:26, Stuart Henderson < s...@spacehopper.org> escribió: > On 2025/07/04 17:49, Jeremie Courreges-Anglas wrote: > > > El vie, 4 jul 2025 a las 4:19, Stuart Henderson > > > (<s...@spacehopper.org>) escribió: > > > > > > > > Perhaps the ports tree came from an older version of ports.tar.gz > from > > > > before the missing files were fixed.. > > > > This ports.tar.gz was generated post-7.7, but was produced using the > > ustar format, not the pax format, so it will lack files with long > > paths/names. > > ah, deraadt regenerated the 7.7 ports.tar.gz and the newer version of > that does use pax, and IIRC when I checked at the time it was complete. > > but it looks like snaps ports.tar.gz still uses ustar. > > (personally I would not bother with ports.tar.gz at all and just fetch > from your friendly local anoncvs mirror). > > > On Fri, Jul 04, 2025 at 09:04:33AM -0600, Maximo Pech wrote: > > > Well, this is strange, I'm grabbing the latest ports.tar.gz from > > > https://cdn.openbsd.org/pub/OpenBSD/snapshots/ and somehow it doesn't > > > contain > patches/patch-src_3rdparty_chromium_services_resource_coordinator_public_cpp_memory_instrumentation_os_metrics_linux_cc > > > > The ports tree tarball hasn't been enough to get a full ports tree > > since years now. (One day, maybe...) You should run cvs up to get > > the missing files. > > > > But I agree with tb: why are you building this yourself? > > yes this is certainly something I would not attempt to build unless > there's no other choice, the packages (and debug packages if needed) > are a better idea for this. >
