Date: Sat, 24 Jul 2004 12:57:07 -0700 From: "David O'Brien" <dev-null@NUXI.com> To: Tobias Roth <roth@iam.unibe.ch> Cc: freebsd-ports@freebsd.org Subject: Re: HEADS UP: change in ports rc.d script behaviour Message-ID: <20040724195707.GA3257@dragon.nuxi.com> In-Reply-To: <20040724193515.GA4208@speedy.unibe.ch> References: <20040724150905.GA998@rogue.acs-et.com> <4102B1BF.4040106@FreeBSD.org> <20040724193515.GA4208@speedy.unibe.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 24, 2004 at 09:35:15PM +0200, Tobias Roth wrote: > guys, this is -CURRENT. it's normal that some changes break other things. > what's the point in complaining this breaking some ports? if you run > -CURRENT on a production box, you usually are aware of what you are > risking. > > also, the time chosen for this upgrade is as good as any. in fact, i even > think this is a good timing, since 5.3 is getting closer. > and it's not mikes responsibility to fix every port this breaks. I'm not so sure -- I often hear complains from Kris about commits in /usr/src that break ports. It seems implied reponsabilty on the /usr/src committer to go help fix the ports. I've seen bsd.port.mk changes held back that broke less ports than this change, simply because the change caused any breakage. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040724195707.GA3257>