From owner-cvs-all@FreeBSD.ORG Mon Mar 15 15:19:01 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BD1816A4CE; Mon, 15 Mar 2004 15:19:01 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C828C43D39; Mon, 15 Mar 2004 15:19:00 -0800 (PST) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 6D20F14734; Mon, 15 Mar 2004 17:19:00 -0600 (CST) Date: Mon, 15 Mar 2004 17:19:00 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Peter Schultz In-Reply-To: <4055BB1E.4010405@bis.midco.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-ports@FreeBSD.org cc: Nakata Maho cc: ports-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Oliver Eikemeier Subject: Re: cvs commit: ports/editors/openoffice-1.1 Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 23:19:01 -0000 > Hey! I'm just grateful the guy is doing this work, and you should be > too. You can install the binary package or even create the private > repository for him, but to criticize him for doing work on this > *incredibly complex* port is just simply WRONG. > > Please restrain yourself! We're lucky he's committing the time and > energy to work on this. If you can't put a positive spin on your > comments, i.e. "I will help you with this" or, "let me know what I can > do," just sit quietly like the rest of us. Oliver by no means "just sits quietly like the rest of us." He is a very active ports committer, which means that he is held to a very strict standard in his commits -- they have to not cause regressions, and they have to not break anything else outside that particular port. He holds other people to the same standards as well (and I should know, he toasted me for several things I missed last week). The philosophy of the ports tree is that (unless the port is postpended with -devel) that it should "just work", or it shouldn't be checked in. And, if a checkin to a -devel port would break something outside the port itself, it doesn't go in either. Without upholding those strict standards, there's no hope of getting the ports tree to work for most people on both OS releases and all the various architectures, and I don't think anyone wants the project to wind up in that situation. mcl