Date: Fri, 6 Nov 1998 15:10:11 -0800 (PST) From: asami@FreeBSD.ORG (Satoshi Asami) To: billf@chc-chimes.com Cc: freebsd-ports@FreeBSD.ORG Subject: Re: bsd.port.mk updates and such Message-ID: <199811062310.PAA10066@silvia.hip.berkeley.edu> In-Reply-To: <Pine.HPP.3.96.981104150505.19007G-100000@hp9000.chc-chimes.com> (message from Bill Fumerola on Wed, 4 Nov 1998 16:15:08 -0500 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
* 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811062310.PAA10066>