From owner-freebsd-ports@FreeBSD.ORG  Thu Jun 19 17:13:45 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7BD02106564A
	for <freebsd-ports@freebsd.org>; Thu, 19 Jun 2008 17:13:45 +0000 (UTC)
	(envelope-from tom@FreeBSD.org)
Received: from eborcom.com (pochard.scrubhole.org [62.3.122.102])
	by mx1.freebsd.org (Postfix) with SMTP id B1D6A8FC16
	for <freebsd-ports@freebsd.org>; Thu, 19 Jun 2008 17:13:44 +0000 (UTC)
	(envelope-from tom@FreeBSD.org)
Received: (qmail 22667 invoked by uid 1001); 19 Jun 2008 16:47:02 -0000
Date: Thu, 19 Jun 2008 17:47:02 +0100
From: Tom Hukins <tom@FreeBSD.org>
To: freebsd-ports@freebsd.org
Message-ID: <20080619164702.GA22382@eborcom.com>
Mail-Followup-To: freebsd-ports@freebsd.org
References: <676047.76296.qm@web32706.mail.mud.yahoo.com>
	<20080619163501.GB12160@atarininja.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080619163501.GB12160@atarininja.org>
User-Agent: Mutt/1.4.2.2i
Subject: Re: regression-test
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2008 17:13:45 -0000

On Thu, Jun 19, 2008 at 12:35:01PM -0400, Wesley Shields wrote:
> Which is why I would recommend wrapping them in checks for
> MAINTAINER_MODE or something similar.  This way you, as the maintainer,
> can turn them on when you want but they don't affect anything else.

That's true for the OS versions and architectures that a maintainer
builds on.

I'm very fond of CPAN's culture of build, test then install for all
modules.  Sure, it takes time, but it's helped me find problems on
machines I use that others, including the author, haven't encountered.

I didn't know Ports had such options until this thread: I'm tempted to
enable regression tests whenever I build ports to benefit from the
extra sanity checking that tests provide.

Restricting such tests to maintainer mode only eliminates these
benefits and risks devaluing MAINTAINER_MODE if non-maintainers set
this variable to benefit from automated testing.

Tom