Date: Mon, 1 Jun 2015 17:05:20 -0400 From: Walt Ford <walt.ford@yahoo.com> To: Julian Elischer <julian@freebsd.org> Cc: freebsd-security@freebsd.org Subject: Re: avoiding base openssl when building ports Message-ID: <20150601210520.GE68495@ws1> In-Reply-To: <556C8BFE.708@freebsd.org> References: <201506010138.t511cp2P088983@gw.catspoiler.org> <alpine.GSO.1.10.1506011214350.22210@multics.mit.edu> <CA%2B7WWSc47cH_C%2BJCFNv22onuf-V=mFNQ%2BU96Gx_vUm-1YU2OdQ@mail.gmail.com> <556C8BFE.708@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 02, 2015 at 12:44:46AM +0800, Julian Elischer wrote: > I'd like to take a bunch of libraries out of base, But That is not the > same as making them "ports". > I've said before that I thik we need something half way between. using > the ports/pkg mechanism, You could just call them supported ports. Supported means what currently happens with 3rd party code in base, and unsupported is what software in ports currently is. But, seems like there still would be an issue with compatibility and a stable API or ABI. If the current restrictions are going away, then you might as well just make them ports. If they're staying, you'll end up with an outdated supported port being maintained separately from the current unsupported port, just like now essentially. -- Skip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150601210520.GE68495>