From owner-freebsd-arch@FreeBSD.ORG  Sun Aug  7 17:21:53 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 6954C16A41F;
	Sun,  7 Aug 2005 17:21:53 +0000 (GMT)
	(envelope-from maxim@macomnet.ru)
Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B74F143D48;
	Sun,  7 Aug 2005 17:21:52 +0000 (GMT)
	(envelope-from maxim@macomnet.ru)
Received: from localhost (localhost [127.0.0.1])
	by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id j77HLZfS027583;
	Sun, 7 Aug 2005 21:21:35 +0400 (MSD)
	(envelope-from maxim@macomnet.ru)
Date: Sun, 7 Aug 2005 21:21:35 +0400 (MSD)
From: Maxim Konovalov <maxim@macomnet.ru>
To: Colin Percival <cperciva@freebsd.org>
In-Reply-To: <42F636BE.3020906@freebsd.org>
Message-ID: <20050807211950.X27563@mp2.macomnet.net>
References: <42F62C5F.6000609@freebsd.org>
	<20050807.101746.68985623.imp@bsdimp.com>
	<42F636BE.3020906@freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: freebsd-arch@freebsd.org
Subject: Re: Adding portsnap to the base system
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2005 17:21:53 -0000

Hi,

[...]
> CVSup in checkout mode, sort of.  Portsnap works using a compressed
> snapshot of the ports tree, which is then used to update /usr/ports,
> and also provides INDEX files; but the job it replaces is basically
> that of cvsup in checkout mode.

Sorry my ignorance but what's about the server side?  Does portsnap
use an existent ftp|www|cvsupd infrastructure or we need to build a
new one?

-- 
Maxim Konovalov