From owner-freebsd-ports  Sat Apr  8 22:48:33 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id WAA03828
          for ports-outgoing; Sat, 8 Apr 1995 22:48:33 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA03818
          for <ports@freebsd.org>; Sat, 8 Apr 1995 22:48:30 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id WAA04234; Sat, 8 Apr 1995 22:48:23 -0700
Date: Sat, 8 Apr 1995 22:48:23 -0700
Message-Id: <199504090548.WAA04234@silvia.HIP.Berkeley.EDU>
To: jkh@freefall.cdrom.com
CC: ports@FreeBSD.org
In-reply-to: <2291.797404496@freefall.cdrom.com> (jkh@freefall.cdrom.com)
Subject: Re: Ports' Makefiles / package names
From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
Sender: ports-owner@FreeBSD.org
Precedence: bulk

 * I prefer it to be implicit, since I can't think of any circumstances
 * in which you _wouldn't_ want the catagory to index the project in a
 * keyword search, but you're the portsmeister now - it's ultimately your
 * decision.  I will abide by whatever solution you come to..

Why do you keep pushing the puck into my court. ;)  Anyway, I think
you're right.  We can just say "KEYWORDS will contain everything in
CATEGORIES as well as anything you define it to be here".

Satoshi