Date: Fri, 25 Aug 2017 09:30:42 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 221770] textproc/p5-XML-Parser: build fails: /usr/local/bin/perl5.24.2 not found Message-ID: <bug-221770-6497-a7Gb5Kd4Am@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221770-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-221770-6497@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=3D221770 --- Comment #2 from MMacD <scratch65535@att.net> --- (In reply to Jan Beich from comment #1) No, it fails because it can't find bin/perl5.24.2. And given the 345,678 p5 ports listed, I've no clue which one would populate that subtree. One of the things I've noticed is that config options never include the cho= ice of excluding some functionality, xml or sound or some other thing, complete= ly.=20 The only options are what *kind* of sound or xml or whatever. I haven't counted, but Firefox must have at least 100 dependencies, few of which have much to do with fetching and displaying web pages (what critical role does = perl play, for example?). And because of the huge number of non-optional "optio= ns", and the lack of resources to do QA, it's a crapshoot whether something will build without bugs, or even at all.=20 Maybe it would be good policy to coarsen the granularity of the config choi= ces? Offer them at the functional level, not the mere-flavoring one? --=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-221770-6497-a7Gb5Kd4Am>