Date: Mon, 31 Aug 1998 02:45:24 -0700 (PDT) From: asami@FreeBSD.ORG (Satoshi Asami) To: ac199@hwcn.org Cc: ports@FreeBSD.ORG Subject: Re: Listing manpages in Makefiles Message-ID: <199808310945.CAA08994@silvia.hip.berkeley.edu> In-Reply-To: <19980829011349.A13277@zappo> (message from Tim Vanderhoek on Sat, 29 Aug 1998 01:13:49 -0400)
next in thread | previous in thread | raw e-mail | index | archive | help
* I said 1) ports should use ``.include "somefile"'' to include the manpage * list. Either that, or we can include it from bsd.port.mk. Just a simple ".if exists(...) .include(...)" so it's not much work either way. * 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". I thought you preferred "pkg/MEN"? :) By the way, do we want a guideline on the format of the file? Something like === MAN1= foo.1 bar.1 baz.1 .... \ blurb.1 blech.1 MAN3= eek.3 yikes.3 .... \ bleep.3 === will minimize the number of lines (and bytes) while === MAN1+= bar.1 MAN1+= baz.1 MAN1+= foo.1 : MAN3+= eek.3 MAN3+= yikes.3 === could reduce the amount of manual labor of upgrading by making it easily scriptable (easy to keep it sorted and using "cvs diff" to see the changes too). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808310945.CAA08994>