Date: Sat, 29 Apr 2000 19:20:54 +0200 From: Neil Blakey-Milner <nbm@mithrandr.moria.org> To: kudzu@tenebras.com Cc: ports@FreeBSD.org Subject: Re: Numerous broken ports Message-ID: <20000429192054.A49130@mithrandr.moria.org> In-Reply-To: <390B16D2.38EB927D@dnai.com>; from kudzu@dnai.com on Sat, Apr 29, 2000 at 10:07:30AM -0700 References: <390B0B02.47368F2A@dnai.com> <20000429185756.A48372@mithrandr.moria.org> <390B16D2.38EB927D@dnai.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat 2000-04-29 (10:07), Michael Sierchio wrote: > > They are checked. Every day, a script builds every port on FreeBSD, and > > makes available the error messages should they fail. > > They shouldn't be included in the ports if they fail. There *is* a central > point of distribution, and there should be some minimum > quality requirement -- like, that it compiles? You still haven't proved that your problems with ports are due to broken ports, as opposed to your system, yourself, your dodgy RAM, or cosmic radiation. I find it unusual that 10 (was it?) ports in a row didn't work for you. Yes, sometimes ports don't work. If they don't work, you report it, with error messages, and they get fixed. It's worked like this for years, and your suggestion that the ports not get distributed if they don't work, while interesting, isn't really an option given how CVS and the FreeBSD development model works. Now, back to business. Where is a copy of your error messages? Neil -- Neil Blakey-Milner Hacker In Chief, Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000429192054.A49130>