From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 19:54:50 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 A451816A4CE; Sat, 24 Jul 2004 19:54:50 +0000 (GMT) Received: from creme-brulee.marcuscom.com (rrcs-midsouth-24-172-16-118.biz.rr.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2957443D48; Sat, 24 Jul 2004 19:54:50 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) i6OJs9KS063251; Sat, 24 Jul 2004 15:54:09 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Tobias Roth In-Reply-To: <20040724193515.GA4208@speedy.unibe.ch> References: <20040724150905.GA998@rogue.acs-et.com> <20040724193515.GA4208@speedy.unibe.ch> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JY76eM4z94mRYueE79ay" Organization: FreeBSD, Inc. Message-Id: <1090698884.76622.16.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 24 Jul 2004 15:54:44 -0400 X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on creme-brulee.marcuscom.com 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 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:54:50 -0000 --=-JY76eM4z94mRYueE79ay Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2004-07-24 at 15:35, Tobias Roth wrote: > [snip questions about breakage and backing out requests] >=20 > 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. >=20 > 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. >=20 > and it's not mikes responsibility to fix every port this breaks. No it is not, but I have asked him to back this out (temporarily) on behalf of portmgr. We do need to give fair warning to all maintainers that are affected. We also need to provide an entry in /usr/ports/CHANGES documenting the new rc.d behavior. Once maintainers have had a chance to fix their affected ports, this can come back into the tree. Joe >=20 > please everyone stop complaining and calm down, or this will end in a > major bikeshed. >=20 > cheers, t. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-JY76eM4z94mRYueE79ay Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBAr6Eb2iPiv4Uz4cRAgfCAKCiOQv9SSeMV0im3iSHOaLZjNG4ogCgmp+0 dL7UknZODcxJoir6saLZuYc= =Ifrj -----END PGP SIGNATURE----- --=-JY76eM4z94mRYueE79ay--