From owner-cvs-all Mon Jul 6 06:59:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12292 for cvs-all-outgoing; Mon, 6 Jul 1998 06:59:40 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12279; Mon, 6 Jul 1998 06:59:35 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id IAA24284; Mon, 6 Jul 1998 08:58:38 -0500 (EST) Date: Mon, 6 Jul 1998 08:58:38 -0500 (EST) From: John Fieber To: Jacques Vidrine cc: Thomas Gellekum , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/devel/py-PyGreSQL - Imported sources In-Reply-To: <199807060737.CAA07643@bone.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Mon, 6 Jul 1998, Jacques Vidrine wrote: > Anyone have descriptions of ports categories/guidelines on > giving ports a home? Carefully look at similar existing ports. If they are consistently placed in a category, place the new port there. Given a choice between consistency and accuracy in classification, consistency is arguably a bit more important in this context. If there is *any* doubt, don't hesitate to post a "where should I put this..." question to ports@freebsd.org. It is much better to do that than move a port after committing it. [Personally I tend to the port categorizations/classification debates. My academic training and most of my real world work experience is in library and information science, so I have some strong opinions on the subject that other have seen as an excessive obsession for splitting hairs. :) ] -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message