From owner-freebsd-ports Fri Nov 6 15:10:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18581 for freebsd-ports-outgoing; Fri, 6 Nov 1998 15:10:29 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18576 for ; Fri, 6 Nov 1998 15:10:27 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-19.ix.netcom.com [205.186.213.19]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA15978; Fri, 6 Nov 1998 15:10:14 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA10066; Fri, 6 Nov 1998 15:10:11 -0800 (PST) Date: Fri, 6 Nov 1998 15:10:11 -0800 (PST) Message-Id: <199811062310.PAA10066@silvia.hip.berkeley.edu> To: billf@chc-chimes.com CC: freebsd-ports@FreeBSD.ORG In-reply-to: (message from Bill Fumerola on Wed, 4 Nov 1998 16:15:08 -0500 (EST)) Subject: Re: bsd.port.mk updates and such From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * problem: * * As anyone who follows this list and the ports PR's knows, people not * having an updated bsd.port.mk is the cause of a LOT of problems for * people. The inability to update this file is caused by several reasons: It is caused by people not reading instructions (or instructions not being clear). The only way to track ports-current (aka ports-stable) is to update your world regularly or use the upgrade kits. Stuffing bsd.port.mk in with the ports collection doesn't solve the problem. There are ldconfig updates, install-info updates (just to name a few) that have broken things in the past. * I track -STABLE on a p75 overdrive, needless to say, I don't build * world everytime there is a change in -STABLE. Though I _could_ (cd * /usr/src/share/mk/ && make install) or add a cron to do that, I don't, and * we can't expect everyone else to either. Get the upgrade kit! :) Seriously, this is just a case of user misconception. Just doing "make install" in src/share/mk is not enough. Ports-current is NOT guaranteed to work with the most recent release. What we need to fix is the documentation. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message