From owner-freebsd-hackers Tue Sep 28 20:40:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 39C06154DA for ; Tue, 28 Sep 1999 20:40:52 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id UAA91933; Tue, 28 Sep 1999 20:40:50 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Sep 1999 20:40:50 -0700 (PDT) From: Doug White To: Mark Shepard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: updating packages automatically... In-Reply-To: <19990928114145.A41493@ed209.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Sep 1999, Mark Shepard wrote: > I _like_ the idea of a email-summary of "What's New in the World of Ports". We used to have this. I think it morphed into the webpage mutation we have now (note you can request all the changed ports in the last X time frame). Maybe it's posted to the -ports mailing list? > - Before I do a "make install", is there some way to > find out exactly which dependencies of the port I'm installing are also > going to need to be upgraded? I think a 'make checkdep' type target to run the dependency check w/o actually building them would be a plus. This should be very easy to do w/ the current bsd.port.mk frame. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message