Date: Fri, 1 Feb 2002 11:03:21 -0500 (EST) From: Mikhail Teterin <mi@aldan.algebra.com> To: tadayuki@mediaone.net Cc: Alexander@Leidinger.net, tadayuki.okada@windriver.com, will@csociety.org, freebsd-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/graphics/gd Makefile pkg-comment Message-ID: <200202011603.g11G3OQ34438@aldan.algebra.com> In-Reply-To: <20020131231749.7515b9eb.tadayuki@mediaone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31 Jan, Tadayuki OKADA wrote: >> > Porter's Handbook demands you to bump PORTREVISION when the package's >> > binary is changed. >> >> Right -- assuming the default (read -- Bento) environment. And it is >> not changing, since Bento builds packages anew from scratch. > I'm talking about when libB.so's major version is bumped. There is > already a package built on bento which depends on old version of > libB.so., and it's already used by many users. And now libB.so's > version is bumped, there's another package built on *bento* > which depends on new libB.so, but that package has exactly same > version-revision with previous one. Well, the current scheme does not guarantee the portrevision bump either. But bento should be basing the decision whether or not to rebuild package on the dependency graph it has (and so should portupgrade, BTW). My proposal has to do with ports building (rather than package installing) and simply extends the same idea, that's now in LIB_DEPENDS -- it does not matter where the library came from, as long as it matches. All I want is to extend the "matching" to regexps, where a maintainer deems useful. > A user can't tell if his package is latest or not by looking at the > package version. You can not have two files with the same path :-) -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202011603.g11G3OQ34438>