From owner-freebsd-ports@FreeBSD.ORG  Mon Mar  3 09:24:24 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 2292D1065670
	for <freebsd-ports@freebsd.org>; Mon,  3 Mar 2008 09:24:24 +0000 (UTC)
	(envelope-from kamikaze@bsdforen.de)
Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79])
	by mx1.freebsd.org (Postfix) with ESMTP id E17A18FC14
	for <freebsd-ports@freebsd.org>; Mon,  3 Mar 2008 09:24:23 +0000 (UTC)
	(envelope-from kamikaze@bsdforen.de)
Received: from mobileKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de
	[129.13.72.169])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.bsdforen.de (Postfix) with ESMTP id 84522405BB3
	for <freebsd-ports@freebsd.org>; Mon,  3 Mar 2008 10:24:22 +0100 (CET)
Message-ID: <47CBC3C5.9050007@bsdforen.de>
Date: Mon, 03 Mar 2008 10:24:21 +0100
From: Dominic Fandrey <kamikaze@bsdforen.de>
User-Agent: Thunderbird 2.0.0.9 (X11/20080228)
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: interactive ports - the plague
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: Mon, 03 Mar 2008 09:24:24 -0000

I don't mind ports that use the config framework. You can deal with them 
without trouble by setting BATCH, using portmaster or portconfig-recursive 
from bsdadminscripts.

But I find ports like ghostscript-gpl that open an ncurses dialogue between 
configure and build stage very annoying. They are the reason one wakes up in 
the morning and finds out that instead of having finished all updates, the 
machine hasn't even started updating, because it's just hanging there, waiting 
with a config dialogue that doesn't even remember what I choose last time.

I cannot find any policy on interactive ports in the Porters' Handbook. Maybe 
there aught to be one.