Date: Tue, 21 May 2002 10:50:06 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: "David O'Brien" <obrien@FreeBSD.org>, Jake Burkholder <jake@locore.ca>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src Makefile.inc1 src/usr.bin/elf2aout elf2aout.c Message-ID: <20020521075006.GC53675@sunbay.com> In-Reply-To: <20020520165910.A77554@dragon.nuxi.com> References: <200205201442.g4KEgnK08485@freefall.freebsd.org> <20020520144724.GB73296@sunbay.com> <20020520121640.B62759@locore.ca> <20020520161035.GQ73296@sunbay.com> <20020520122736.C62759@locore.ca> <20020520172004.GA96582@sunbay.com> <20020520165910.A77554@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--DSayHWYpDlRfCAAQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 20, 2002 at 04:59:10PM -0700, David O'Brien wrote: > On Mon, May 20, 2002 at 08:20:04PM +0300, Ruslan Ermilov wrote: > > > > > A better change would be to mfc the endian changes. I find what = you did > > > > > kind of disgusting. I also would have preferred if you asked me = before > > > > > committing it. > > > > >=20 > > > > Even if we MFC it today, this stuff wouldn't have fixed the upgrade= path > > > > from systems that do not (and never will) have sys/endian.h like 5.= 0-CURRENT > > > > before sys/endian.h was added, and all released 4.x versions. >=20 > To upgrade from 4.x to 5.0, one should pass thru top of RELENG_4 tree. >=20 Not anymore. > Anything else is not agreed to by all of us. I do not like many of the > warts^H^H^Hhacks you put in the build system to handling 4.0->5.0 source > upgrading. >=20 These "hacks", as you call them are called bootstrapping. > Please discuss this issue on arch@ and lets come to a consensus. >=20 OK. > > Yes, and it works now. Even if you forget about 4.x for the moment, > > the "old pre-<sys/endian.h> 5.0" still holds. >=20 > People with very old -current's should know how to get around nits like > this (make includes for instance); otherwise they should consider a > binary upgrade. > =20 "make includes" is _incorrect_ step; /usr/include must be compatible with your currently running kernel and libs. Bootstrapping is the technique that allows us to compile a selected set of programs that we use during the build and install (bootstrapping =3D=3D upgrade) to compile in the host environment (with old includes, libraries, and kernel). Depending on how long you want the upgrade path be, it may require more or less bootstrap supporting code. What you don't perhaps seem to realize is that merging the said program (elf2aout) and adding it to bootstrap tools would create the same set of problems for 4.x, and expecting -stable users to "know how to get around" the broken upgrade path from 4.1 to say 4.6 isn't a good option. > > I expect that by time we release 5.0, we will officially support > > X.any -> X+1.0 upgrade paths (including cross-updates). >=20 > Uh, no. Discuss this amongst all the developers before you push your > personal desire on all of us. >=20 I would probably scare you, some would even like to see FreeBSD can build on any POSIX.1-YYYY compliant system. :-) Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --DSayHWYpDlRfCAAQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE86fwuUkv4P6juNwoRAkbDAJ97qsLHT7lwDuFxvhX7Q/yTtYpBKwCcCq3P /1Pkq46/Ji2bhYe0Apl3w+Q= =oZ+5 -----END PGP SIGNATURE----- --DSayHWYpDlRfCAAQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020521075006.GC53675>