Date: Mon, 1 Apr 1996 10:00:45 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: davidg@Root.COM Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Subject: Re: We need to do another XFree86 release for -current someday soon.. Message-ID: <199604011700.KAA13606@phaeton.artisoft.com> In-Reply-To: <199603312246.OAA07341@Root.COM> from "David Greenman" at Mar 31, 96 02:46:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> In general this is true. In this case, however, we made a conscious and > deliberate decision to stop supporting the code. This coupled with the > consensus that broken and unsupported code should be removed rather than > fester in the source tree is what led to its removal. > The "2.2" release is a long way off and we'll likely have other reasons for > bumping the library major number before the release happens. If people want to > run code that is 6-9 months away from release, then they should be prepared to > deal with a few "bumps" along the way. This has always been our stated policy > about -current, so nothing 'new' here. > I fully support the removal of code from libc as well as the major number > bump. We have a policy of providing backward compatibility via our "compat" > distributions and we'll continue to support older binaries with this mechanism. > Future XFree86 releases should be built against RELEASE versions of FreeBSD. I > believe this has always been their policy, so nothing 'new' here, either. Are stubs being written for "compat"? Or will the libraries not fail catastrophically (for instance, for an older netstat)? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604011700.KAA13606>