John, Adrian, On Tue, Nov 05, 2013 at 05:18:26PM -0500, John Baldwin wrote: J> Mmmm, people run older versions of binaries (even open source ones) on newer OS's J> perhaps more often than you think. The COMPAT_43 stuff can be dropped certainly, J> but people will almost certainly do rolling upgrades where they upgrade the OS J> on their machines before they upgrade their packages.
On Tue, Nov 05, 2013 at 02:25:13PM -0800, Adrian Chadd wrote: A> My main worry about this kind of work is that you're just steamrolling A> through stuff that yes, should be done, but with little warning and no A> API deprecation schedule. A> A> I'd much rather see this stuff handled more formally - we mark the API A> as deprecated and remove it in the next release. A> A> I really don't like seeing steamrolling through the kernel and A> deprecating APIs with minimal warning and having no (optional) A> backwards compatibility implementations. That's what made us stand out A> from Linux - we kept old APIs around as much as we could. Linux wasn't A> terribly good at this. One reply to both of you. The schedule is the following: we are compatible with previous major version. The interface had changed in early 10.0-CURRENT, and during the entire 10.0-CURRENT life it has supported the new and the old interface and this went into stable/10. When doing the change, I have pronounced this deprecation schedule. If anyone upgrades to next major: 9.x -> 10.x, or 10.x -> 11.x, including package sets, then everything will be working for him. -- Totus tuus, Glebius. _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
