From owner-freebsd-doc@FreeBSD.ORG Wed Dec 22 08:59:28 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E790716A4CE for ; Wed, 22 Dec 2004 08:59:27 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9155443D31 for ; Wed, 22 Dec 2004 08:59:27 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 23CCC148F2; Wed, 22 Dec 2004 02:59:27 -0600 (CST) Date: Wed, 22 Dec 2004 02:59:27 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: freebsd-doc@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: CFD: one more patch to the Committer's Guide X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 08:59:28 -0000 there is now some duplicate text in the the Committer's Guide that has to do with creating a new ports category (the other text moved to the Porter's Handbook). This patch removes it -- but, while here, adds the last few (?) forgotten details of this (really involved) procedure. I would appreciate any review (and I promise not to forget to include fixes like I did for Denis ...) mcl Index: article.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v retrieving revision 1.219 diff -u -r1.219 article.sgml --- article.sgml 22 Dec 2004 07:54:15 -0000 1.219 +++ article.sgml 22 Dec 2004 08:56:14 -0000 @@ -2654,16 +2654,29 @@ - A developer who wishes to propose a new category - should submit a detailed rationale for the new category, - including why existing categories are not sufficient, - and the list of ports proposed to move. - - Before submitting, keep in mind that there is a fair - amount of work involved from multiple parties; that the - changes affect everyone who wants to keep up-to-date with - the entire ports tree; and that such proposals tend to - attract controversy. + Please see + + Proposing a New Category in the Porter's Handbook. + Once that procedure has been followed and the PR has been + assigned to &a.portmgr;, it is their decision whether or + not to approve it. If they do, it is their responsibility + to do the following: + + + + Perform any needed repocopies. + + + + Update the VALID_CATEGORIES + definition in ports/Mk/bsd.port.mk. + + + + + Assign the PR back to you. + + @@ -2676,18 +2689,6 @@ The procedure is a strict superset of the one to repocopy individual ports (see above). - File a PR in GNATS, listing the - reasons for the category request. Preferably, this should - also include patches for Makefiles for - the old ports, the Makefiles for their - old categories, and the VALID_CATEGORIES - definition in ports/Mk/bsd.port.mk. - Assign the PR to the &a.portmgr; (as portmgr). - If they approve it, it will be reassigned to &a.cvsadm; (as - cvs), who will do a repository copy from - the old to the new locations and reassign the PR back to you. - Once everything is done, perform the following steps: - Upgrade each copied port's @@ -2785,14 +2786,37 @@ cvsup/sup/ports-categoryname: list.cvs and releases. (Note: these are - in the src, not the ports, repository). + in the src, not the ports, repository). If you + are not a src committer, you will need to submit + a PR for this. - Submit a docs PR to add the new category to both the + Update the documentation by modifying the + following: + + + + the - Porter's Handbook and to + list of categories in the Porter's Handbook + + + + www/en/ports/categories. + + + + the section of the Handbook that lists the + + cvsup collections. + + + (Note: these are + in the docs, not the ports, repository). If you + are not a docs committer, you will need to submit + a PR for this.