Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Oct 2006 08:15:21 -0700
From:      Chris <snagit@cbpratt.prohosting.com>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Portsnap Update Question
Message-ID:  <E4BA4B1E-4404-468C-AB62-169D90B16109@cbpratt.prohosting.com>
In-Reply-To: <200610061557.41452.list-freebsd-2004@morbius.sent.com>
References:  <2403D229-1D39-40F8-9C40-01A7DEF8ED5D@cbpratt.prohosting.com> <200610061557.41452.list-freebsd-2004@morbius.sent.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On Oct 6, 2006, at 7:57 AM, RW wrote:

> On Friday 06 October 2006 15:14, Chris wrote:
>
>> I've been doing is then running portsnap fetch update to apply
>> patches to the ports. In doing so, I've not seen recompilations take
>> place and remained somewhat fuzzy as to whether I was merely
>> retrieving snapshots of source for whatever is in /usr/ports or if in
>
>
> You aren't even doing that. The ports tree is just a set of recipes  
> that tells
> the ports system how to get hold of the source and build the software
> automatically. When you run portsnap or cvsup (with a ports  
> supfile) you are
> simply updating those recipes.

Thanks all, major misunderstanding on my part. It's likely a problem  
with my ability to understand the documentation but I'd taken it to  
be an alternate method of keeping ports current. If I understand  
correctly, portsnap is only allowing the ports to install correctly  
in subsequent cd /usr/ports/*;make install sessions and adding new  
pointers for ports added to the tree.

I found a cookbook on portupgrade and will research portaudit next.

Thanks again.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?E4BA4B1E-4404-468C-AB62-169D90B16109>