From owner-freebsd-ports Sat Aug 15 18:11:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13564 for freebsd-ports-outgoing; Sat, 15 Aug 1998 18:11:56 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from localhost.my.domain (ppp1718.on.bellglobal.com [206.172.249.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13556 for ; Sat, 15 Aug 1998 18:11:53 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id VAA05473; Sat, 15 Aug 1998 21:10:32 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 15 Aug 1998 21:10:32 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Scott Blachowicz cc: Tim Vanderhoek , freebsd-ports@FreeBSD.ORG Subject: Re: ports/7617: update mail/nmh port to nmh-0.27 In-Reply-To: <199808152353.QAA09318@two.sabami.seaslug.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 15 Aug 1998, Scott Blachowicz wrote: > > 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? Almost. ;-) Once committed, it'll still take a while to hit the web. > > [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... Unfortunately, no. Simply snarfing the newest bsd.port.mk will effectively upgrade you, for the moment. I presume eventually that a standard upgrade-your-ports-system-from-227 package will be available, courtesy asami. > Hmmm...I've been CVSUP'ing the ports collection - I don't see bsd.port.mk in src/share/mk/bsd.port.mk > 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). I don't know. I guess a special collection would have to be added for bsd.port.mk. I think only jdp and asami are supposed add new collections, so don't look at me. :-) On a more practical note, the next easiest way of keeping up-to-date would be to fetch ftp://ftp.FreeBSD.ORG/pub/FreeBSD/src/share/mk/bsd.port.mk regularly. -- 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