From owner-freebsd-ports Fri Aug 28 22:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11634 for freebsd-ports-outgoing; Fri, 28 Aug 1998 22:15:01 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from localhost.my.domain (ppp6477.on.bellglobal.com [206.172.208.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11612 for ; Fri, 28 Aug 1998 22:14:52 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id BAA18612; Sat, 29 Aug 1998 01:13:50 -0400 (EDT) (envelope-from tim) Message-ID: <19980829011349.A13277@zappo> Date: Sat, 29 Aug 1998 01:13:49 -0400 From: Tim Vanderhoek To: ports@FreeBSD.ORG Subject: Listing manpages in Makefiles Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sometime during the recent bsd.port.mk changes, I suggested that ports with a long list of manpages in their Makefile should list them in an outside file instead. The reason for this, of course, is that some ports have a ridiculous number of lines listing nothing but manpages (consider EZWGL with some 200 lines of nothing but manpages). Listing the manpages at the end of the Makefile instead of at the beginning of the Makefile is not an option. I said 1) ports should use ``.include "somefile"'' to include the manpage list. 2) there should be a very-well-established guideline on the name of "somefile". 3) there should be a guideline on how many lines are saved before using ``.include "somefile"'' is endorsed. [Satoshi agreed with these three points]. 4) the ``.include "somefile"'' line should be placed in the same place as the MANx variables would normally appear in the Makefile. I would like to propose that the filename used be "files/manpages". For the guideline on how many lines must be saved, 6 or more. This guideline would be documented in porting.sgml, but not enforced. The use of "files/manpages" could be enforced at random times. Violators would be punished by slapping them silly. Any other suggestions or objections, speak now! Since my modifications to the EZWGL making it use MLINKS also use these new guidelines, they will go into practice when the MLINKS modifications are committed. (Unless someone beats me to using these guidelines :). -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message