From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 19:57:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94AE316A4CE; Sat, 24 Jul 2004 19:57:09 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E5EC43D2D; Sat, 24 Jul 2004 19:57:09 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i6OJv8gF009800; Sat, 24 Jul 2004 12:57:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i6OJv8Gg009799; Sat, 24 Jul 2004 12:57:08 -0700 (PDT) (envelope-from obrien) Date: Sat, 24 Jul 2004 12:57:07 -0700 From: "David O'Brien" To: Tobias Roth Message-ID: <20040724195707.GA3257@dragon.nuxi.com> References: <20040724150905.GA998@rogue.acs-et.com> <4102B1BF.4040106@FreeBSD.org> <20040724193515.GA4208@speedy.unibe.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040724193515.GA4208@speedy.unibe.ch> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 X-Mailman-Approved-At: Sat, 24 Jul 2004 20:35:27 +0000 cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: HEADS UP: change in ports rc.d script behaviour X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2004 19:57:09 -0000 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)