Port upgrading - my way

[Kirk Strauser]

On Tuesday 21 September 2004 12:40, Curtis Vaughan wrote:

> Then I run:
>
> portupgrade -a
>
> That's it.

You missed the most important middle step:

    less /usr/ports/UPDATING

to see what critical changes have been made in the meantime that will affect 
your system.  For example, the www/apache2 port recently disabled the 
various mod_proxy modules by default.  Since my company's site depends on 
those, I would have been in a mess if I hadn't planned to handle that 
change before running the portupgrade.
-- 
Kirk Strauser
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040921/745c6b37/attachment.bin