From owner-freebsd-ports Sat Aug 15 17:23:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08478 for freebsd-ports-outgoing; Sat, 15 Aug 1998 17:23:13 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from mx.seanet.com (dns2.seanet.com [199.181.164.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08438 for ; Sat, 15 Aug 1998 17:23:04 -0700 (PDT) (envelope-from scott@two.sabami.seaslug.org) Received: from two.sabami.seaslug.org (sab.seanet.com [199.181.166.94]) by mx.seanet.com (8.8.8/Seanet-8.7.3) with ESMTP id RAA26602; Sat, 15 Aug 1998 17:22:30 -0700 (PDT) Received: from two.sabami.seaslug.org (localhost [127.0.0.1]) by two.sabami.seaslug.org (8.8.5/8.6.12) with ESMTP id QAA09318; Sat, 15 Aug 1998 16:53:11 -0700 (PDT) Message-Id: <199808152353.QAA09318@two.sabami.seaslug.org> To: Tim Vanderhoek cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/7617: update mail/nmh port to nmh-0.27 References: <199808152030.NAA18821@freefall.freebsd.org> In-reply-to: <199808152030.NAA18821@freefall.freebsd.org> From: Scott Blachowicz Reply-to: Scott.Blachowicz@seaslug.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9280.903225189.1@two.sabami.seaslug.org> Date: Sat, 15 Aug 1998 16:53:10 -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > if sendfiles(1) is a new man page that comes with the update then this > > change should be reflected in the Makefile, and the PLIST should have the > > gzip'd version. > > No, it shouldn't be listed at all in the PLIST, presuming you are > correctly using the MAN? variables. Is correct use documented in the handbook or in bsd.port.mk? > ... > Again, presuming the MAN? variables are correctly used for all of > those manpages, none of them should be listed in the PLIST. > > [You need, of course, the latest bsd.port.mk] Is the latest in the 2.2.7 release that I just received? I've been lax in updating my BSD system at home (it's still at 2.2.2) and had been meaning to update to 2.2.6 when I heard that 2.2.7 was on its way... Hmmm...I've been CVSUP'ing the ports collection - I don't see bsd.port.mk in there. Would it make any sense to have a special directory in there for control/maintenance files (e.g. bsd.port.mk), so it would get picked up by CVSUP'ing the ports? Or should I add a little magic incantation to my /etc/cvsupfile to snag the needed files (I don't need/want all of the src dist). Scott.Blachowicz@seaslug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message