Date: Tue, 21 Feb 2017 11:03:11 -0500 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: Mathieu Arnold <mat@FreeBSD.org>, Jan Beich <jbeich@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: Misuse of PORTREVISION (Re: svn commit: r434379 - head/multimedia/x265) Message-ID: <d5e81c35-41fe-4f5c-4f45-e069d93ce911@aldan.algebra.com> In-Reply-To: <a9be8749-360f-15fb-aa75-93a378371c51@FreeBSD.org> References: <20170218210541.82AA915F6@freefall.freebsd.org> <f23cecfc-d669-e62b-1916-1e16e66fb3eb@aldan.algebra.com> <a9be8749-360f-15fb-aa75-93a378371c51@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21.02.2017 10:52, Mathieu Arnold wrote:
>> Just did. But I believe, our usage of PORTREVISION is wrong-headed.
> I completely agree. The problem is that portupgrade/portmaster do not
> handle shlib bumps and do not force rebuilding depending ports. If you
> want to fix those tools to behave in a better way, please do so.
I'm neither the author nor a maintainer of these tools. But I'm glad we
agree on the underlying problem.
> In the mean time, when some shlib version is bumped, all consumers must
> have their PORTREVISION bumped.
The tools have been broken in this manner /for years/ -- why would they
ever change, if PORTREVISION is bumped every time? And, when it is not,
PortMgr-officials go hunting the offender -- instead of the actual
authors/maintainers of the broken tools?
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5e81c35-41fe-4f5c-4f45-e069d93ce911>