From owner-cvs-ports@FreeBSD.ORG Thu Feb 7 23:37:31 2008 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1B6116A420 for ; Thu, 7 Feb 2008 23:37:31 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 851E913C478 for ; Thu, 7 Feb 2008 23:37:31 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 6167 invoked from network); 7 Feb 2008 23:37:31 -0000 Received: from aldan.algebra.com (HELO aldan-mlp) ([216.254.65.224]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 7 Feb 2008 23:37:30 -0000 From: Mikhail Teterin Organization: Virtual Estates, Inc. To: "Jeremy Messenger" Date: Thu, 7 Feb 2008 18:37:28 -0500 User-Agent: KMail/1.7.1 References: <200802070531.m175VikU015939@repoman.freebsd.org> <200802071801.38477.mi+mill@aldan.algebra.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200802071837.29761.mi+mill@aldan.algebra.com> Cc: cvs-ports@freebsd.org, pav@freebsd.org, Norikatsu Shigemura , cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: obsoleteing PORTREVISION bumps (Re: cvs commit: ports/devel/icu) X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Feb 2008 23:37:31 -0000 =DE=C5=D4=D7=C5=D2 07 =CC=C0=D4=C9=CA 2008 06:10 =D0=CF, Jeremy Messenger = =F7=C9 =CE=C1=D0=C9=D3=C1=CC=C9: > What about the users that who are using ports, not packages? What about them? Which scenario do you foresee breaking? > The PORTREVISION is needed or/and add info in /usr/ports/UPDATING about = =9A > reinstall these ports that depend on icu. I don't think, PORTREVISION bump is needed in these cases -- only when the= =20 port itself is changed. Any changes due to build-dependencies=20 (lib-dependencies among them) should be tracked independently. -mi