Date: Thu, 7 Feb 2008 22:29:24 -0200 (BRST) From: garga@freebsdbrasil.com.br To: "Mikhail Teterin" <mi+mill@aldan.algebra.com> Cc: Jeremy Messenger <mezz7@cox.net>, Norikatsu Shigemura <nork@freebsd.org>, cvs-all@freebsd.org, ports-committers@freebsd.org, pav@freebsd.org, cvs-ports@freebsd.org Subject: Re: obsoleteing PORTREVISION bumps (Re: cvs commit: ports/devel/icu) Message-ID: <12565.BUtXBwYWXFY=.1202430564.squirrel@webmail.freebsdbrasil.com.br> In-Reply-To: <200802071837.29761.mi%2Bmill@aldan.algebra.com> References: <200802070531.m175VikU015939@repoman.freebsd.org> <200802071801.38477.mi%2Bmill@aldan.algebra.com> <op.t56f0ir79aq2h7@mezz.mezzweb.com> <200802071837.29761.mi%2Bmill@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> четвер 07 лютий 2008 06:10 по, Jeremy Messenger Ви написали: >> 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 >> >> reinstall these ports that depend on icu. > > I don't think, PORTREVISION bump is needed in these cases -- only when the > port itself is changed. Any changes due to build-dependencies > (lib-dependencies among them) should be tracked independently. I disagree with you, i believe one of the most important ports feature is to make sysadmins life easier. Sure, you need to read UPDATING before update ports, but, it makes much more sense to bump the PORTREVISION of dependant ports, when a lib version bumps, it makes life easier and sounds more organized to me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12565.BUtXBwYWXFY=.1202430564.squirrel>