Date: Mon, 2 Dec 2002 10:17:15 +0200 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: "M. Warner Losh" <imp@bsdimp.com> Cc: dcs@newsguy.com, current@FreeBSD.ORG, re@FreeBSD.ORG, dougb@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: [REPORT] Upgrade from 4.0-RELEASE to 5.0-CURRENT Message-ID: <20021202081715.GA83484@sunbay.com> In-Reply-To: <20021201.111129.35672010.imp@bsdimp.com> References: <20021201150303.GA6369@sunbay.com> <3DEA2774.DCE1CACD@newsguy.com> <20021201.111129.35672010.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 01, 2002 at 11:11:29AM -0700, M. Warner Losh wrote: > In message: <3DEA2774.DCE1CACD@newsguy.com> > "Daniel C. Sobral" <dcs@newsguy.com> writes: > : There I go reply to all... <sigh> > :=20 > : IIRC, we never supported upgrade to 4.0 or 4.1 from anybut but the > : *latest* version in the 3.x series. I sure hope we adopt the same policy > : here. >=20 > ru@ has stepped up to the plate to support more. He's gone through > and made sure that all the way back to 4.0-release is upgradable (at > least at each release point), going to support it through the first > branchpoint. You as a committer aren't required to do extra work to > make this work, except to not remove things he's done to make this > work. It is unclear what should happen when a piece of thirdparty > software is upgraded. However, core ruled a long time ago that ru@ > can take reasonable measures to make sure that it works. ru@ has kept > it up for a while now, so it looks like he's in it for the long run. >=20 > This is only for native builds. Anything that is needed for cross > building isn't included in this 'upgrade' path. It is there just to > make our user's life easier. Also, core didn't want the work arounds > to get too gross, but so far all the ones I've l ooked at were > relatively inobtrusive. >=20 Um, why? I can even cross-build any of our supported arches on the 4.0-RELEASE i386 box. This happens almost automatically, as part of the cross-arch work tasks. Cross-releases have some issues, and the Alpha box (of any useful sort) would help me a lot in polishing this. I've asked donations@ about this when they were offered a bunch of Alpha boxes last month, but haven't heard from them back. 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 --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE96xcLUkv4P6juNwoRAnqeAJ9HMMl/FQMS1BbueOvmhEBo6mSDrQCfQFVm YeL54ypZomso+A7q/dNS048= =1b8e -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021202081715.GA83484>