Date: Sat, 8 Apr 1995 18:44:53 -0700 From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: jkh@freefall.cdrom.com Cc: ports@FreeBSD.org Subject: Re: Ports' Makefiles / package names Message-ID: <199504090144.SAA03452@silvia.HIP.Berkeley.EDU> In-Reply-To: <12905.797339944@freefall.cdrom.com> (jkh@freefall.cdrom.com)
next in thread | previous in thread | raw e-mail | index | archive | help
* > (3) The MAINTAINER line. This is mandatory! Write
* > "ports@FreeBSD.ORG" if you don't feel like personally taking care
* > of it (although we hope you would :).
*
* But it already defaults to that.. :-)
I know....I just wanted people to be explicit about their intentions,
so that I don't have to go chase every port without a Makefile just to
have the committer say "but you said I can leave it empty if I don't
want to take care of it".... ;)
* Don't forget that it's also convention to have KEYWORDS be a superset
* of CATEGORIES (it's set to ${CATEGORIES} now, as the default). I
* would either recommend that people setting KEYWORDS explicitly include
* them like this:
*
* KEYWORDS+= ${CATEGORIES} raisins sex chainsaws
*
* Or that we make KEYWORDS be KEYWORDS+= ${CATEGORIES} instead of
* KEYWORDS?= ${CATEGORIES} as it is now.
This is a very good point. Which way should we go? I prefer letting
the user add it explicitly, but you are the one who came up with these
two variables....Jordan?
* > Here are some examples on how to convert a ${DISTNAME} into a suitable
* > ${PKGNAME}:
*
* Ditto. It's religious, but a standard is fine by me! :-)
:)
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504090144.SAA03452>