From owner-freebsd-ports@FreeBSD.ORG  Sun May 23 09:26:38 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9A0DA16A4CE; Sun, 23 May 2004 09:26:38 -0700 (PDT)
Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id F0CC743D1D; Sun, 23 May 2004 09:26:36 -0700 (PDT)
	(envelope-from sem@ciam.ru)
Received: from ppp8-103.pppoe.mtu-net.ru ([81.195.8.103] helo=ciam.ru)
	by mail.ciam.ru with asmtp (Exim 4.x)
	id 1BRvnh-000I3B-Kq; Sun, 23 May 2004 20:26:13 +0400
Message-ID: <40B0D0AB.2070406@ciam.ru>
Date: Sun, 23 May 2004 20:26:19 +0400
From: Sergey Matveychuk <sem@ciam.ru>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7b) Gecko/20040421
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Josef Karthauser <joe@FreeBSD.org>
References: <20040523100634.GB42932@genius.tao.org.uk>
In-Reply-To: <20040523100634.GB42932@genius.tao.org.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: ports@freebsd.org
Subject: Re: config interface and ports.
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
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: Sun, 23 May 2004 16:26:38 -0000

Josef Karthauser wrote:
> I'm wondering what the process is to convert ports to use the new
> 'config' interface.  For example postfix doesn't appear to save it's
> configuration to /var/db/ports.  Is it easy to fix, or does the port
> require a restructuring?  Can anyone point me to the relevant
> documentation?

OPTIONS is still in develpment state and will be changed soon (I hope).
It can be used with some restrictions if port maintainer is itching for 
it. Like me :)

-- 
Sem.