using /etc/portsnap.conf

Polytropon freebsd at edvax.de
Thu Jan 3 06:14:28 UTC 2013


On Wed, 2 Jan 2013 18:24:14 +0000 (UTC), Walter Hurry wrote:
> By the way, in answer to your question in another thread, you don't have 
> to extract the whole tree if you don't want to. Use 'portsnap fetch' the 
> first time around, and then portsnap extract the port you want. See 'man 
> portsnap', and remember to cater for the dependencies.

This is correct and works in many many situations. However,
there has been a saying which states that "only a complete
ports tree is guaranteed to work properly"; I think this
basically refers to the availability of dependencies and
turtles all the way down, plus the top level files (such
as /usr/ports/Makefile) and the Mk/ and Tools/ subtrees.


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


More information about the freebsd-questions mailing list