> On 01/08/2013 00:28, Chris H wrote: > >> In the first instance, /usr/ports was removed (before initiating portsnap). >> But before >> the second attempt, I performed a mkdir /usr/ports. But in the end, the >> results were >> the same; >> portsnap fetch fetched the image, verified the image, >> extracted to /var/db/portsnap/ports, then patched, and exited. >> I did _not_ issue portsnap fetch && portsnap extract. >> So I guess portsnap extract is a noop. Guess it's time to update the >> portsnap(8) >> man pages to indicate portsnap fetch is no longer an option. > > 'portsnap fetch' downloads the relevant data to /var/db/portsnap > 'portsnap extract' extracts the files to /usr/ports > 'portsnap update' updates existing files in /usr/ports > > So on a clean system you use portsnap fetch extract > Then to update later you use portsnap fetch update > > (you can give multiple commands to portsnap in one go) > > If fetch extract works on amd64 and not i386 then you should submit a > problem report so that it can be fixed. Greetings, Yes, I know. That's how it's _supposed_ to work. :) I guess a send(2) pr is in order.
Thanks for the reply. --chris > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
