Date: Tue, 30 Jan 2001 16:52:49 -0500 From: Will Andrews <will@physics.purdue.edu> To: Matthew Emmerton <matt@gsicomp.on.ca> Cc: ports@FreeBSD.ORG Subject: Re: 40upgrade.tgz Message-ID: <20010130165249.C452@puck.firepipe.net> In-Reply-To: <007001c08b02$07cdfef0$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Tue, Jan 30, 2001 at 04:17:19PM -0500 References: <20010130101146.A18917@mooseriver.com> <20010130183014.72885.qmail@mail.oregonfast.net> <20010130140537.A452@puck.firepipe.net> <20010130111703.A513@mooseriver.com> <007001c08b02$07cdfef0$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--/e2eDi0V/xtL+Mc8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 30, 2001 at 04:17:19PM -0500, Matthew Emmerton wrote: > Has anyone informed the www/doc team that the link to 40upgrade.tgz is > broken from http://www.freebsd.org/ports/index.html? >=20 > I'm also a bit confused by what is discussed above. Will makes it sound > like a 4.0-REL system needs both 40upgrade.tgz AND 41upgrade.tgz, which to > me doesn't sound correct - 40upgrade.tgz should move a 4.0-REL system up = to > 4-STABLE (as of date of downloading the upgrade kit) as far as ports are > concerned, and not requires two upgrade kits. Well, it is because each one takes care of two different problems.. it is kinda tough to merge back changes and compile them on an older system. So.. the older the OS that the upgrade tarball targets is, the more difficult it is to update it. So for the most part these things rely on binary compatibility to work. Plus, it may not be as simple as checking out the HEAD version of pkg_install and compiling it on a 4.0 box.. (though pkg_install/* usually works, but some other things don't). In any case, these bootstrapping packages probably should be done better. IMO, the PKGORIGIN thing shouldn't be required (and to be honest, the amount of code that the "base package tools" cover should be much smaller, so we could just package the extra stuff like PKGORIGIN and just tell people to upgrade their package tools). Some things are unavoidable.. e.g. libc and/or libc_r upgrades. Those are much more difficult to work around other than upgrading via buildworld... --=20 wca --/e2eDi0V/xtL+Mc8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6dzexF47idPgWcsURArrCAJ0epnND5Sv77j666tGjM3dmFyazLgCgmNAM iAqt7vFhy//NQn1GGj64keg= =uWhs -----END PGP SIGNATURE----- --/e2eDi0V/xtL+Mc8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010130165249.C452>