From owner-freebsd-arch@FreeBSD.ORG Sat Aug 27 18:56:44 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C70816A41F for ; Sat, 27 Aug 2005 18:56:44 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: from useful.dataloss.nl (useful.dataloss.nl [80.84.249.161]) by mx1.FreeBSD.org (Postfix) with SMTP id C968443D45 for ; Sat, 27 Aug 2005 18:56:43 +0000 (GMT) (envelope-from peter@dataloss.nl) Received: (qmail 20875 invoked by uid 1001); 27 Aug 2005 18:56:40 -0000 Date: Sat, 27 Aug 2005 20:56:40 +0200 From: Peter van Dijk To: freebsd-arch@freebsd.org Message-ID: <20050827185639.GA20018@dataloss.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: portsnap base thought X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2005 18:56:44 -0000 Hi, portsnap requires that the /usr/ports on a machine was created with portsnap extract, before it will allow you to portsnap update. Suggestion: make the portstree as delivered in 6.0-RELEASE (on the CD etc.) compatible with portsnap extract, so people can use portsnap from a base CD install without having to fetch the portstree through portsnap first. I do realise this might bloat the CD image by about 50 megabytes (because of /var/db/portsnap) but I think it's worth it. Cheers, Peter -- peter@dataloss.nl | ~ tonight tonight, what is this potion http://blog.dataloss.nl/ | ~ that makes a fool of me UnderNet/#clue | Wayfinder, fr-025 soundtrack