Date: Thu, 08 Sep 2011 18:54:36 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: sysutils/cfs Message-ID: <4E68F34C.6090504@FreeBSD.org> In-Reply-To: <4E68AC85.4060705@icritical.com> References: <4E651DCF.30605@FreeBSD.org> <201109052146.p85Lkous037023@fire.js.berklix.net> <CADLo838dMd5=TjRF5ffiaPH7o0%2BpeWgaqbQqEfDb3EP-n4ec8A@mail.gmail.com> <4E67935C.6080702@aldan.algebra.com> <CADLo838QkAjq2jPXy_c5MTYW09tZJMvWTNndo3Pnfa3=1c-5Og@mail.gmail.com> <4E68AC85.4060705@icritical.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 08.09.2011 13:52, schrieb Matt Burke: > Changing to a hypothetical example, why would an Apache vulnerability in > mod_rewrite in the least bit bother a person who doesn't have the module > enabled, which I believe is the standard configuration? Would you prefer > Apache be deleted from ports if it took longer than expected to fix it? That wouldn't happen anyways because the package is actively maintained, unlike many of the ports the discussion is about. > What the current FreeBSD policy of actively deleting perfectly usable ports > instead of putting a mild hurdle in the way is saying, is that FreeBSD will > stop me doing what I may want to do because FreeBSD knows best. The port isn't perfectly usable (because that would mean it's usable in all circumstances for all advertised purposes, which is explicitly not the case in the light of known vulnerabilities). > I want machines, tools, to do as *I* say not the other way round, whether > it's good for me or not. If I wanted nannying and interference, I'd install > Ubuntu. No, you'd use a managed installation. Nobody stands there pointing a gun at your head and forces you to uninstall a port that got removed from the ports/ tree. If people could recognize that, it might help get the derailed discussion back on the right track.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E68F34C.6090504>