Date: Wed, 28 May 2008 13:54:32 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Daniel Eischen <deischen@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Xin LI <delphij@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/include string.h src/lib/libc/string Makefile.inc memchr.3 memrchr.c src/sys/sys param.h Message-ID: <20080528135432.363f363d@kan.dnsalias.net> In-Reply-To: <Pine.GSO.4.64.0805281114320.7240@sea.ntplx.net> References: <200805272004.m4RK4SZt029194@repoman.freebsd.org> <20080528091745.465f37b4@kan.dnsalias.net> <Pine.GSO.4.64.0805281114320.7240@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/hSmzVtW.FXXWNcn5XmP0a.z Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 28 May 2008 11:39:21 -0400 (EDT) Daniel Eischen <deischen@freebsd.org> wrote: > Interesting, as long as "a" =3D ".1", so that you have FBSD_1.0.1 as > the side version. >=20 > See my prior email - I thought we agreed that we just MFC the version > (in this case, FBSD_1.1) from -current. If you introduce a new > version, a binary built on 7.x may not run on -current from before > the side version was added. For instance, if we were to add > memfoo() in -current now, then we release 8.0 with memfoo@@FBSD_1.1, > then after the release we MFC memfoo() to RELENG_7 in the way > you describe, then anything built in RELENG_7 using memfoo() will > not work in 8.0 release (because 8.0 didn't have the side version > memfoo@@FBSD_1.0a/1.0.1). >=20 > Typically before a release there are a flurry of MFCs, so you can > have a few months or more elapse before the addition of new or > ABI-changed symbols. If we just use the same version as -current, > then things will just work, at least from when the symbol was > changed/added in -current. There are number of corners we can cut if we agree that being sloppy is not a problem. Then why did we bother with symbol versions in the first place? =20 > But regardless, I think this means that once we release 8.0, we > cannot MFC any new or changed symbols (from 8.0+) back to > 7.x. If someone upgrades from 7.x to 8.0, then 8.0 has to > have all the symbols that 7.x will have or else binary > compatibility will be broken. > That is why introducing new symbols in back-releases is not such a hot idea. Release X that was released after release Y cannot really be expected to be able to execute Y's binaries with 100% certainty, as that depends on guessing the future right at X ship time. --=20 Alexander Kabaev --Sig_/hSmzVtW.FXXWNcn5XmP0a.z Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFIPZxYQ6z1jMm+XZYRAtt3AJ4zPPYKVxpyUCI4NS5ovJ+6Qk0ltwCfT8aE vFRe1nqG3VFea55T92nyBCI= =Qdk5 -----END PGP SIGNATURE----- --Sig_/hSmzVtW.FXXWNcn5XmP0a.z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080528135432.363f363d>