Same version on binary packages and updated ports
rwmaillists at googlemail.com
Fri Dec 30 13:15:01 UTC 2011
On Thu, 29 Dec 2011 19:53:25 +0100
Walter Alejandro Iglesias wrote:
> I really appreciate that you all, Jerry, Polytropon and Chuck,
> took your time to answer me. But I think some of you understood
> paragraphs like individual-separated statements, that's why you
> did not fully understand my question (my horrible English helps
> too :-)).
> Let's see if I can explain myself.
> I know that FreeBSD base system and 3rd party are "managed"
> separately. For RELEASE I meant the ports included in a fresh
> RELEASE install. The scenario is: what to do after a fresh
> RELEASE install. Once you updated the ports with 'portsnap fech
> extract update' you have newer versions at the port tree. Then
> you can upgrade the already installed software using
> portupgrade... But compiling!
One strategy is to use csup to only update the port tree to release
tags and so use successive release packages as you update the base
system. You need to check portaudit for vulnerabilities.
An alternative is to use stable packages. There are two problems with
this. The first is that whilst these packages will mostly work they are
not guaranteed to be compatible with release, or older stable, base
systems. You can eliminate this entirely by using stable and updating
world after updating the ports tree.
The second problem is the variable lag between a port being
updated and the package becoming available. Frequent updating
exacerbates this problem. If you use portupgrade -P every day it will
probably never use a package file.
If it's for a production server, you might consider building your own
packages on a separate machine.
More information about the freebsd-questions