portsnap update won't update original /usr/ports

RW rwmaillists at googlemail.com
Thu May 24 00:35:41 UTC 2012

On Tue, 22 May 2012 21:30:44 -0400 (EDT)
Thomas Mueller wrote:

> ----- Original Message -----
> From: Gary Aitken <freebsd at dreamchaser.org>
> To: freebsd-questions at freebsd.org
> Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT)
> Subject: portsnap update won't update original /usr/ports
> According to the handbook, one can do
>    portsnap fetch
>    portsnap update
> and the update will work with a previously created ports tree;
> I presume this includes one created during system install.

It says:

"If you are running Portsnap for the first time, extract the snapshot
into /usr/ports: # portsnap extract

If you already have a populated /usr/ports and you are just updating,
run the following command instead..."

If you have the tree from the disk then that means you are running
portsnap for the first time, the second sentence refers to a /usr/ports
populated by a portsnap extract.

> ---- My response: ----
> Now I wonder if it's feasible to switch between "portsnap fetch
> update" and csup <ports-supfile>, or if it's strictly one or the
> other.

You'll probably get away with it most of the time, but it's not safe to
mix them.

More information about the freebsd-questions mailing list