From owner-freebsd-ports@FreeBSD.ORG Wed Dec 3 03:25:08 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED5C11065678 for ; Wed, 3 Dec 2008 03:25:08 +0000 (UTC) (envelope-from jktrigg@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id BF5E68FC0A for ; Wed, 3 Dec 2008 03:25:08 +0000 (UTC) (envelope-from jktrigg@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so3536115wfg.7 for ; Tue, 02 Dec 2008 19:25:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=Pzc0jcU6/CgecujbJy3m6/2XQh9jpJSdD95htQzht1w=; b=a+O2uhkHpFxEwVRBruOHebiGvKqqhwh4eI64NZpwDx35O9CXx3eWAIXyrsaXDCpaWk RqmhNU2oKXtnU2DdvCipTg3kH4wOhNsyDpRidOsY8QXPBHVwBCNx6S3yxLyq+P1jAsH1 9ORXY8hG87tSONTjjsvhzuBVX62GUzwJRC/Dw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=LZWnj+iNRYl3FAOyeh/I9ew1n6vh7FM5ILd3x1TFctyQMQS+nBTnzjNHaq95z6TUG2 rFReVGOoKOlWC7x0YsW9RvB+lno3gwMaf198d+NQhEg1yqHZa1JT9OmjN+LGPSnOH6Ta Tn5uOPgFOpWb2Z00drCqU0/vRjYJHPHoy9vWs= Received: by 10.142.226.10 with SMTP id y10mr5159884wfg.3.1228273389128; Tue, 02 Dec 2008 19:03:09 -0800 (PST) Received: by 10.142.238.21 with HTTP; Tue, 2 Dec 2008 19:03:08 -0800 (PST) Message-ID: <87ef649b0812021903x7e2d3ee9h90dde2dcffe4e2be@mail.gmail.com> Date: Tue, 2 Dec 2008 22:03:08 -0500 From: "Jim Trigg" Sender: jktrigg@gmail.com To: freebsd-ports@freebsd.org In-Reply-To: <20081203020857.523645bc@gumby.homeunix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081202180743.GB70240@hades.panopticon> <20081203020857.523645bc@gumby.homeunix.com> X-Google-Sender-Auth: 0a61d39e7923267e Subject: Re: Proposal: mechanism for local patches X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 03:25:09 -0000 On Tue, Dec 2, 2008 at 9:08 PM, RW wrote: > I wonder if portsnap actually needs to behave the way it does. > > Portsnap stores its compressed snapshot as one .gz file for each > port plus one for each additional file (files in Mk/ etc). When you > do an "update" any modified snapshot files are extracted over > the appropriate location in the ports tree. > > The reason that "portsnap extract" deletes patch-files is that before > each .gz file is extracted, the corresponding file or port directory is > deleted. I wonder why, if an "update" can decompress over the top of a > port, an "extract" need to delete it first. I can't think of any good > reason offhand. > > Modifying portsnap not to delete extra files is just a matter of > deleting one line. The behaviour of portsnap extract would then be > virtually identical to csup. Alternately, it wouldn't be much harder to > create a new portsnap command. I would presume that it does that to get rid of "standard" patch files that are no longer part of the port... Jim Trigg