Keeping Ports synchronised with Packages

Andrew L. Gould algould at
Thu Apr 22 06:29:27 PDT 2004

On Thursday 22 April 2004 07:41 am, Richard Bradley wrote:
> Hi all,
> I am getting the impression that I am using the ports and packages system
> the wrong way, but can't find a good tutorial on how to use them to their
> best. I would be quite happy to write one up, but I need to understand it
> first!
> My problem is that my ports tree is always a couple of minor versions ahead
> of the available packages.
> (I use `cvsup /usr/share/examples/cvsup/ports-supfile` as suggested in the
> handbook)
> If I add a program with e.g.
> #portinstall gaim
> it compiles it from source, and updates a load of libraries and dependent
> ports to the current versions.
> This means I have a load of libraries that are different versions to those
> the precompiled packages expect, and some packages even refuse to install.
> I end up having to install more and more things from the ports, which is
> slooow (do you have any idea how long it takes to compile kde?) and creates
> even more problems if I try to use a package.
> What am I doing wrong? Is there a way to hold back cvsup to the same
> version as the packages on
> On a related note, where do the errors from sysinstall go? It refers to the
> "debug screen" but I can't find it on any terminal. What about if you run
> it in a konsole or xterm?
> Any pointers would be much appreciated.
> All the best,
> Rich

The way to update your system source and hold back package/port versions is to 
refuse ports.  See:

Alternatively, you can continue to cvsup ports and then upgrade your packages 
to newer versions using the port portupgrade, which can be found 
at /usr/ports/sysutils/portsupgrade.

Best of luck,

Andrew Gould

More information about the freebsd-questions mailing list