https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295993
--- Comment #16 from Alastair Hogge <[email protected]> ---
Some history (Not for you Dag-Erling, your classic domineering, dismissive, and
dissuading characteristics has achieved it's aim here, so you need not reply,
tho I doubt that). I switched to read-only ${SRC} ~19 years ago because the
build would pollute the source tree, causing problems. Over the years
occasional mails to current mailing list still illustrate that this problem
still exists. The additional advantages to using a read-only mount on tmpfs it
reduces wear on SSDs for people such as myself living just above the poverty
line, or perhaps people who like to value longevity for their electronics, or
both, or avoid using slow spinning rust, or maybe other reasons.
This problem still exists, and was even recently noted[1] by a seasoned uncle
of the project:
> Times when a clean build is needed should be rare and either we fix the underlying problem, or we document the problem.
I have personally found that having a sterile build dir, one that is easily
nuked from tmpfs has helped narrow down problems with increasing the rate which
I can iterate on looking for the source of a problem.
1: https://lists.freebsd.org/archives/freebsd-current/2026-August/010613.html
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.