From owner-freebsd-ports-bugs@FreeBSD.ORG  Fri Jan  2 08:30:25 2004
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 817D516A4CE
	for <freebsd-ports-bugs@hub.freebsd.org>;
	Fri,  2 Jan 2004 08:30:25 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9F63E43D45
	for <freebsd-ports-bugs@hub.freebsd.org>;
	Fri,  2 Jan 2004 08:30:24 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	i02GUOFR058701	for <freebsd-ports-bugs@freefall.freebsd.org>;
	Fri, 2 Jan 2004 08:30:24 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i02GUOxv058700;
	Fri, 2 Jan 2004 08:30:24 -0800 (PST)
	(envelope-from gnats)
Date: Fri, 2 Jan 2004 08:30:24 -0800 (PST)
Message-Id: <200401021630.i02GUOxv058700@freefall.freebsd.org>
To: freebsd-ports-bugs@FreeBSD.org
From: kaeru@inigo-tech.com
Subject: Re: ports/60689: Naming convention
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: kaeru@inigo-tech.com
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>,
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>,
	<mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2004 16:30:25 -0000

The following reply was made to PR ports/60689; it has been noted by GNATS.

From: kaeru@inigo-tech.com
To: freebsd-gnats-submit@FreeBSD.org, kaeru@inigo-tech.com
Cc:  
Subject: Re: ports/60689: Naming convention
Date: Sat, 03 Jan 2004 00:25:34 +0800 (MYT)

 I looked at the another exiting CMF port www/cmfforum, and also at other
 python ports eg. databases/PyGreSQL which use mixed cased
 name convention. Zope/CMF have their own mixed cased naming
 convention, and I thought it was better to follow than create
 a new one as it would be easier to look for those ports.
 
 Also Zope/CMF ports also have multiple words such as CMFPhotoAlbum,
 CMFExternalFile, CMFFormController etc. These would become something like
 zope-cmfformcontroller, zope-cmfexternalfile which isn't very readable.
 
 I'm a first time porter, so I'm not sure what's best. Should it be:
 
 zope-cmfformcontroller
 zope-cmf-formcontroller
 zope-CMFFormController
 
 Please advice, and I will patch my PR's with the desired FreeBSD ports
 naming convention.