From owner-freebsd-stable@FreeBSD.ORG Mon Jan 28 18:53:48 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 087E6D45 for ; Mon, 28 Jan 2013 18:53:48 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id BEA761D8 for ; Mon, 28 Jan 2013 18:53:47 +0000 (UTC) Received: from [128.206.184.213] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.6/8.14.6) with ESMTP id r0SIrgDB077696; Mon, 28 Jan 2013 12:53:42 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <5106C936.1040301@missouri.edu> Date: Mon, 28 Jan 2013 12:53:42 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Isaac (.ike) Levy" Subject: Re: svn - but smaller? References: <20130123144050.GG51786@e-Gitt.NET> <20130124111332.GA29105@server.rulingia.com> <1359343502-3377760.86081485.fr0S3OcBl026861@rs149.luxsci.com> <5105F684.501@missouri.edu> <1359380102-3423267.83606864.fr0SDYbB5022353@rs149.luxsci.com> <51068698.1010302@missouri.edu> <1359382681-308951.083326822.fr0SEH1A4010109@rs149.luxsci.com> In-Reply-To: <1359382681-308951.083326822.fr0SEH1A4010109@rs149.luxsci.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Peter Jeremy X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 18:53:48 -0000 On 01/28/13 08:17, Isaac (.ike) Levy wrote: > On CTM: > > On Jan 28, 2013, at 9:09 AM, Stephen Montgomery-Smith wrote: >>> - I'm wondering if there is a clean/reliable way to pull an index of the CTM deltas? (This is still very far from the one-liner c[v]sup had become, it would be great to check for new delta files in a simple automated manner.) >>> >> >> Not sure what you mean. You can do "ctm -l file-name" and it will tell >> you what files are modified in that delta. And for ports, you have the >> usual "make fetchindex." But that is about it. > > I'm sorry I wasn't clear enough- I meant: > On the FTP server, is there an index of which CTM delta files are on the FTP server? I'd like to automate fetching just the new deltas... > > If there was perhaps 1 file with a consistent name, I could fetch that on a nightly basis and fetch the other CTM files. I can easily put in something like this. Maybe the output of ls in each directory? If you have more ideas on this, sign up to the ctm-users mailing list, and we can discuss exactly what is wanted. > >>> - does CTM go away with the CVS servers, e.g. who/how is it supported supported and maintained going foreword under SVN? >>> >> >> No. CTM is now completely dependent on svn. I create the CTM deltas on >> a computer owned by the University of Missouri. > > Cool. > Is there any redundancy for this process, for example, deltas being created out on the east/west mirrors? Perhaps as an SVN post-commit hook? No. The deltas are created in one place. And they are created every 16 hours according to a rigid schedule.