From owner-freebsd-questions@FreeBSD.ORG Tue Apr 20 19:23:09 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA986106566B for ; Tue, 20 Apr 2010 19:23:09 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (113901-app1.sourcehosting.net [72.32.213.11]) by mx1.freebsd.org (Postfix) with ESMTP id 84E538FC13 for ; Tue, 20 Apr 2010 19:23:09 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1O4J2J-000DMS-3X; Tue, 20 Apr 2010 15:23:08 -0400 Received: from [127.0.0.1] (fireball.entropy.prv [192.168.1.12]) by cube.entropy.prv (Postfix) with ESMTP id 54FF43EB103E; Tue, 20 Apr 2010 15:23:06 -0400 (EDT) Message-ID: <4BCDFEF0.4030106@FreeBSD.org> Date: Tue, 20 Apr 2010 15:22:24 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Joe Auty References: <20100419185300.55218.qmail@joyce.lan> <4BCCAA33.5040500@FreeBSD.org> <4BCCAE5E.2060407@netmusician.org> <4BCCB9EE.9030503@FreeBSD.org> <4BCDF7C9.9090303@netmusician.org> <4BCDF94A.2070302@FreeBSD.org> <4BCDFC3B.5010600@netmusician.org> In-Reply-To: <4BCDFC3B.5010600@netmusician.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=1C940290 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) Cc: freebsd-questions@freebsd.org Subject: Re: Questions about port revision numbers, portsnap, csup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2010 19:23:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joe Auty wrote: > Greg, > > After applying the update (which I noticed was available immediately > after my last response to you, sorry about that!), everything is just > peachy now, or at least not causing the segfaults, thanks! > > Not to sound unappreciative and purely in the spirit of being > constructive, I'd suggest a little more specificity as far as what a > "break" is on the commit history. This goofy title was created because > it didn't occur to me that the break fix committed on April 12 was only > for compilation. I would suggest specifying whether the break and the > fix is for compiling, or for the software to work properly > post-compilation. This would have saved me a little confusion and time. > > > Again, you kick ass, in no way do I want this to sound harshly critical, > I hope this can be taken as purely constructive :) > > Thanks again for your help with this fix! > Hi Joe, Great, I'm glad to hear that's working for you now. I do appreciate your input, re: commit logs. "Unbreak" is too nebulous, and I'll plan to add further info like "fixed compiler error" in the future. I admit we were in a bit of a rush to get various PHP modules building again after the PHP 5.3.2 update, and I somehow missed the fact that this one supported 5.3.2 with a new release of itself. I think I'll be better prepared for this kind of thing in the future! Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLzf7v0sRouByUApARAockAKC61isslQlss2C03zRPbovtBG6H9QCgkOFE g2xUYqmTQvdFXZibSEgi5A0= =qfdq -----END PGP SIGNATURE-----