Upgrade to 4.8 RELEASE

Jud judmarc at fastmail.fm
Thu Oct 23 09:22:35 PDT 2003


On Thu, 23 Oct 2003 09:21:13 -0400, "Jesse Guardiani" <jesse at wingnet.net>
said:
> Jud wrote:
> 
> > On Sat, 18 Oct 2003 20:04:39 -0400, Robert H. Perry
> > <rperry4 at earthlink.net> wrote:
> 
> [...]
> 
> > Unless there is a specific reason not to do so, cvsup and make world would
> > seem to be an easier and altogether better way to go for an upgrade from
> > one minor version number to the next.  Many users do this quite routinely
> > (e.g., I do it once every week or two).  See <URL:
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html#CUTTING-EDGE-SYNOPSIS>.
> > While this section of the Handbook talks about the "cutting edge"
> > development branches, -CURRENT and -STABLE, the same process can be used
> > to upgrade to a -RELEASE.
> 
> Do you find it impossible to install binary packages after such an
> update?
> Do you have to use ports after such an update?
> 
> I could never get packages to install properly after cvsuping my source.
> I'm wondering if this is somehow by design, or if I did something
> wrong... ?

Last question first: IIRC, you were a bit confused regarding ports vs.
packages, so the reason for failure of packages (or perhaps it was
ports?) to install properly may be as simple as typing commands meant for
ports when you really wanted to install a package, or vice versa. 
Installing a package is as easy as typing 'pkg_add' followed by a URL, or
a directory location if you've downloaded the package first.  Installing
a port is also quite easy - just cd to the port's directory and type
'make install clean.'

If you cvsup the -CURRENT or 5.x base system sources and make world, then
packages expecting a 4.x base system won't install properly.  However
(again, IIRC), Mr. Perry was contemplating an update from 4.7 to 4.8, so
packages built for 4.x should install fine.

Jud


More information about the freebsd-questions mailing list