40GB WRKOBJDIR is too tight if you end up with two chromium-based ports

built on the same machine, suggest 50 min on archs with chromium and that
100 wouldn't be unreasonable

diff --git a/share/man/man8/bulk.8 b/share/man/man8/bulk.8
index 35f8d96..a9cba53 100644 (file)
--- a/share/man/man8/bulk.8
+++ b/share/man/man8/bulk.8
@@ -1,4 +1,4 @@
-.\"    $OpenBSD: bulk.8,v 1.9 2024/05/16 10:14:22 tb Exp $
+.\"    $OpenBSD: bulk.8,v 1.10 2024/05/16 10:31:55 sthen Exp $
 .\"
 .\"    Copyright (c) 2016 Marc Espie <espie@openbsd.org>
 .\"
@@ -59,11 +59,14 @@ for instance
 .Pp
 Reserve one "scratch" partition under the chroot for WRKOBJDIR
 (for instance, mfs, async, or SSD).
-This partition should be roughly 40GB if you want to be able to
-build all ports using multiple CPU cores.
 This can often double as
 .Pa /tmp
 under the chroot.
+The largest ports can take in excess of 20GB each (more for a debug
+build) and you may have several of these built at the same time.
+50GB is probably a reasonable minimum on an architecture which can build
+chromium, though 100GB would not be overkill, especially if you have
+many cores.
 .Pp
 Alternately, you can setup your whole chroot as a scratch partition,
 and reserve one more permanent space under it for distfiles,