From owner-freebsd-ports@FreeBSD.ORG Mon Jan 27 06:56:04 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 02285A12; Mon, 27 Jan 2014 06:56:04 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BBD5716FA; Mon, 27 Jan 2014 06:56:03 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id q10so5376131pdj.38 for ; Sun, 26 Jan 2014 22:56:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s1oIb3kQVm4JKJHwTriiqQHQnwd0IC9iLebM7NChdM8=; b=LE6TJdylF82eUEsT7lT6UJJAQXt4pbcqN8ZrpnnWmzLqWotR63VFVqdU1z6JW5/My7 /qWdgLiKHscIRE5rpUM0Y6uU0xgMCW5k3bbllfbwBgfG8F5US87IdLVebEV0tplJkN4T NmwuYgWB+09vgWtVD5phP9Zi5QEyvL0r8SlYW25tfFlyDU1wt5BflUgP7GsFfCmDQaqL X7lhx9VgynIycxcLOzqoZrbqyTDagqT98d6EnsHDlIJknePRDVIhHvH9gYiVS/mjXxfG aJE5dZpv+haHclzNQ0QWHt+VZ3LaSviukaq7/qlcxei8Vdi1StSNCSXZcYnsFxr0yjxC jJAw== MIME-Version: 1.0 X-Received: by 10.68.240.36 with SMTP id vx4mr1459437pbc.140.1390805763421; Sun, 26 Jan 2014 22:56:03 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 26 Jan 2014 22:56:03 -0800 (PST) In-Reply-To: <52E5F14B.4060102@freebsd.org> References: <52E43A80.4030501@rawbw.com> <52E44BC1.7040404@rawbw.com> <52E46D44.6050403@freebsd.org> <52E47EF7.7040402@ohlste.in> <52E55186.7020009@freebsd.org> <52E55361.3000108@freebsd.org> <52E5757F.8000604@freebsd.org> <52E5CBDD.4090803@freebsd.org> <52E5F14B.4060102@freebsd.org> Date: Mon, 27 Jan 2014 01:56:03 -0500 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Aryeh Friedman To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 06:56:04 -0000 On Mon, Jan 27, 2014 at 12:40 AM, Alfred Perlstein wrote: > > I'm not sure, I'm going to go load up healthcare.gov to see if I can > order myself some free aspirin after this "discussion". > At least my build system has never caused me to need an aspirin (normal debugging is bad enough). Sarcasm aside, to bring this thread back on track, the important issues are: * The development model used by aegis is likely the cleanest development cycle I have seen (main reason for this is Peter Miller is one of the few SCM and build management theorists [vs. just hacking something til it works]). The model is namely (repeat as needed) develop->test->review->integrate... note that test comes before review for the simple reason to even get to review you must build correctly and pass all your own tests (isn't this the main goal of automating the port system anyways)... also keep in mind we can use this model without necessarily switching to aegis per se. With or without aegis, it would save the ports team a lot of time to be able to build and test a port automatically before they spend any time reviewing the code. Aegis, by default, enforces this model. * GitHub *REQUIRES* all developers (including all port maintainers -- not just the committers) to switch to GitHub. On the other hand, if the ports team were to use aegis and/or cook, this would NOT require any changes at all from the POV of maintainers. Even on the ports team, most members would need to learn nothing more than 6 new basic commands... (portmgr@would need to learn a lot more though depending on what kind of non-standard processing needs to be done in integration). * If there are modifications to the overall port system, switching to aegis and/or cook would not require changes to individual ports like GitHub seems to > I skimmed the rest of your message and nothing really stuck out as > something worth perusing. I guess I have to say is that I hope you enjoy > Agis so much that you and the 10 other people using it are able to > proselytize it to the success that git and github have had. You certainly > seem passionate about it! > It would be nice if you could refrain from commenting on stuff you can't be bothered to "peruse." -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org