Date: Sun, 11 Dec 2016 17:35:54 -0500 From: <scratch65535@att.net> To: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Message-ID: <odkr4cdf8dant07thrav2ojn7bng98noj9@4ax.com> In-Reply-To: <20161208085926.GC2691@gmail.com> References: <c5bc24cc-5293-252b-ddbc-1e94a17ca3a8@openmailbox.org> <20161208085926.GC2691@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have to admit that I avoid ports if at all possible because I've hardly ever been able to do a build that ran to completion. There's always some piece of code that's missing and can't be found, or is the wrong version, et lengthy cetera. I've never done release engineering, but I honestly can't imagine how some of the stuff that makes its way into the ports tree ever got past QA. It would get someone sacked if it happened in industry. If the dev schedule would SLOW DOWN and the commitment switched to quality from the current emphasis on frequency, with separate trees for alpha-, beta-, and real release-quality, fully-vetted code, the ports system might become usable again.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?odkr4cdf8dant07thrav2ojn7bng98noj9>