portmaster -af fails due to dead port - HELP

Polytropon freebsd at edvax.de
Fri Jul 3 23:06:58 UTC 2015

On Fri, 03 Jul 2015 18:28:56 -0400, Baho Utot wrote:
> Just have to learn how to run STABLE/CURRENT.

Update your sources using SVN and follow the instructions
provided in /usr/src/Makefile's header - that's all. :-)

Also have a look at the documentation:






Before freebsd-update was present, this was the preferred way
to update your OS. When you want to follow -STABLE or -CURRENT,
it's still the way to go. Basically it's just a "make update"
and a few other commands.

> It would be nice if the base system was also in pkg, but you can't have 
> everything.

This is because the OS is not a package, and it's not made from
packages. Instead it's coming from its own source tree (different
from what and how ports are being built).

This is a common misconception or misunderstanding often found
in Linux land where there is no distinction between "the OS"
and "3rd party applications"; instead the OS is made from a
selection of packages (where the distribution creator decides
which package format and which packages to use to construct
the "base system", quotes intended), and even the kernel can
be considered a package. A failed updating process of "everything"
(which usually means "update my applications") can render the
whole system unusable. On FreeBSD, damaged ports do not affect
the OS, it's still operational.

The FreeBSD OS is "standardized" and maintained by different
people than those responsible for the ports collection.

You can see the wisdom in the fact that "everything else" is
located in /usr/local, whereas the top level directory entries
belong to the operating system. Delete /usr/local entirely and
the OS will still boot and run. See "man hier" for details.

That's why the OS cannot be accessible via pkg. :-)

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list