Date: Mon, 06 Jun 2022 12:59:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 264454] Do not build TEST_DEPENDS in case NO_TEST is set and do not run tests Message-ID: <bug-264454-7788-wK6yQyc4Ol@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264454-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-264454-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264454 --- Comment #9 from Bjoern A. Zeeb <bz@FreeBSD.org> --- You go by assumptions of what people are doing. I do not do port upgrades; in fact I most often never do apart from select individual bits which I do not handle this way. I build coherent image (tailored distribution) after FreeBSD version bumps = on main at times (I am not even doing every one of them). I do have ports which are not in FreeBSD, I have ports which in fact build bootable images bundled all together. The only thing I noticed was that build times and built packages over time (especially in the last year) massively increased on a system which also wo= rked ages and is documented as such and I finally started looking. Can we get away from use whatever other tools available to actually fixing = the problems at hand one way or another or otherwise close the PR as "won't fix" and save the time of repeated discussions. I am happy to call the problem different if you have a problem that it is titled "NO_TEST" as I indicated before. But it seems there are more people than just me using recursive targets. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264454-7788-wK6yQyc4Ol>