From owner-freebsd-ports@FreeBSD.ORG Mon Sep 1 20:30:59 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B480D480 for ; Mon, 1 Sep 2014 20:30:59 +0000 (UTC) Received: from mail.lunabase.org (mail.lunabase.org [173.255.212.186]) by mx1.freebsd.org (Postfix) with ESMTP id 9C58E1DA7 for ; Mon, 1 Sep 2014 20:30:59 +0000 (UTC) Received: from praxis.lunabase.org (cpe-172-249-196-215.socal.res.rr.com [172.249.196.215]) by mail.lunabase.org (Postfix) with ESMTPSA id 72A0342298; Mon, 1 Sep 2014 13:30:53 -0700 (PDT) Message-ID: <5404D76F.10205@lunabase.org> Date: Mon, 01 Sep 2014 13:30:39 -0700 From: Ted Faber User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: How to submit a port update? References: <5401F646.6030304@lunabase.org> <20140830175001.GS9400@home.opsec.eu> <54023CF9.1040002@lunabase.org> <20140830212321.GV9400@home.opsec.eu> <540250CF.5010803@lunabase.org> <20140831075059.GW9400@home.opsec.eu> In-Reply-To: <20140831075059.GW9400@home.opsec.eu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pvxaVo3K4aQKKOpiciscivi9ORbWalfaA" Cc: faber@lunabase.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2014 20:30:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pvxaVo3K4aQKKOpiciscivi9ORbWalfaA Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 08/31/2014 12:50 AM, Kurt Jaeger wrote: > Hi! >=20 >> The update is mostly some small changes to the code to eliminate clang= ++ >> and recent g++ warnings along with Eric's typo, which has been >> languishing for a while. I know it's a small thing, but seeing those= >> warnings when I compile the port makes me sad. Obviously you guys can= >> reject if you don't feel it's worth it. >=20 > Well, it's always nice to check process and procedures while it's > not time-critical 8-} >=20 > And you are right, the porters handbook still mentions send-pr. >=20 > There is one thing which is very nice to have for an incoming PR: > poudriere test logs that prove that the updated port builds cleanly. >=20 > If you never used poudriere, have a look at this short starter guide: >=20 > https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/using_testport.wik= i >=20 >> That changes the port diff, of course. The new one is attached, or I >> can update bugzilla. >=20 > Always update bugzilla (says the guy who preferres mail...) >=20 >> Sorry to bug you if it's too trivial a change. >=20 > No, it's fine. I guess I would only release new versions if runtime bug= s > or runtime functionality changes. You also updated the autotools > environment, maybe that fixes other stuff as well. >=20 > You re-rolled the distfile without a version change, this is not > purrrfect, but well, what else is 8-) >=20 Thanks for all your help. I see that the update went through. Next time I'll include the pourdriere logs. Thanks! --=20 http://www.lunabase.org/~faber Unexpected attachment? http://www.lunabase.org/~faber/FAQ.html#SIG --pvxaVo3K4aQKKOpiciscivi9ORbWalfaA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQE128ACgkQaUz3f+Zf+XusawCdGOY1qTVIX104lXP/PgMzCABM WqgAmwXNWxQiFiXi1f9eV2O2iznxM2jv =zfeg -----END PGP SIGNATURE----- --pvxaVo3K4aQKKOpiciscivi9ORbWalfaA--