From owner-freebsd-ports@FreeBSD.ORG Wed Jan 4 18:21:04 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13FE51065676; Wed, 4 Jan 2012 18:21:04 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id DBD9A8FC0C; Wed, 4 Jan 2012 18:21:03 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=imac.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1RiVSJ-0003MG-6a; Wed, 04 Jan 2012 13:20:57 -0500 Received: from imac.entropy.prv (localhost [127.0.0.1]) by imac.entropy.prv (Postfix) with ESMTP id 4CC0BD4A2ED; Wed, 4 Jan 2012 13:21:00 -0500 (EST) Message-ID: <4F04988C.6010008@FreeBSD.org> Date: Wed, 04 Jan 2012 13:21:00 -0500 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.25) Gecko/20111213 Lightning/1.0b2 Thunderbird/3.1.17 MIME-Version: 1.0 To: Bernhard Froehlich References: <4F0373EC.7060305@FreeBSD.org> <1eb890f6a9d7608aa1b899e89ac1727c@bluelife.at> In-Reply-To: <1eb890f6a9d7608aa1b899e89ac1727c@bluelife.at> X-Enigmail-Version: 1.1.1 OpenPGP: id=1C940290 X-SA-Exim-Connect-IP: 68.189.245.235 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL, BAYES_00, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: ports@freebsd.org Subject: Re: redports.org - The public FreeBSD ports development infrastructure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 18:21:04 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/4/12 3:07 AM, Bernhard Froehlich wrote: > On 03.01.2012 22:32, Greg Larkin wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 12/29/11 6:44 AM, Bernhard Froehlich wrote: >>> Hi Porters! >>> >>> I am happy to announce that redports.org has finally >>> reached the point where I think It's safe to be used >>> by everybody! In case you never heard of it before >>> redports is the result of an idea born at EuroBSDCon >>> 2011 in Karlsruhe to give Port Maintainers and Port >>> Committers a public service to test their new ports >>> or ports patches during development or before >>> submitting a ports PR. >>> >> [...] >> >> Wow! Stellar job, Bernhard, and I'm looking forward to using >> redports.org for fixing ports that are broken under clang. > > Hope you don't want to do that today because during the night the > current building machine paniced and needs someone power cycling > it. I will do this in the evening so no builds today :( > > It looks like I could get some hardware from portmgr so > hopefully more hardware and redundancy is available soon. > >> I noticed one minor typo on https://redports.org/buildgroups: >> automaticaly -> automatically > > Thanks, it's fixed now! > Hi again Bernhard, It looks like ports are building fine now. As I was building the first port on your system, I thought of an enhancement, and I am interested to know how difficult it would be to implement. I maintain various p5- and py- ports, and I often want to test them under multiple versions of Perl and Python, in case there are conditional behaviors in the Makefile. Assuming you're not planning on allowing users to create their own builds, what about adding the ability to set build variables in a make.conf file? For instance, if I commit etc/make.conf to my personal repository location, redports would overlay my options before starting the build. Then I could do things like force Python version 2.7, Perl version 5.10, etc. What do you think? Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8EmIsACgkQ0sRouByUApAegQCgxgLcmbZihiQUtUj2TzYXPhrY xncAoLZ19vyGQP1bPnaNdfbNa6Gm6Bcg =Bus6 -----END PGP SIGNATURE-----