Date: Sat, 18 Feb 2017 21:05:41 +0000 (UTC) From: jbeich@freebsd.org (Jan Beich) To: mi@FreeBSD.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r434379 - head/multimedia/x265 Message-ID: <20170218210541.82AA915F6@freefall.freebsd.org> In-Reply-To: <201702181942.v1IJgO11071590@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mikhail Teterin <mi@FreeBSD.org> writes: > Author: mi > Date: Sat Feb 18 19:42:23 2017 > New Revision: 434379 > URL: https://svnweb.freebsd.org/changeset/ports/434379 > > Log: > Upgrade from 2.2 to 2.3. [...] > +++ head/multimedia/x265/pkg-plist Sat Feb 18 19:42:23 2017 (r434379) > @@ -3,5 +3,5 @@ include/x265.h > include/x265_config.h > lib/libx265.a > lib/libx265.so > -lib/libx265.so.102 > +lib/libx265.so.110 Can you bump PORTREVISION in consumers? multimedia/ffmpeg recently enabled X265 by default but tools relying on "pkg version" may not notice the change which would leave users with an error e.g., $ mpv --no-config /path/to/foo.mp4 Shared object "libx265.so.102" not found, required by "libavcodec.so.57" According to https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html#makefile-portrevision Examples of when PORTREVISION must be bumped: Version bump of a port's shared library dependency (in this case, someone trying to install the old package after installing a newer version of the dependency will fail since it will look for the old libfoo.x instead of libfoo.(x+1)).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170218210541.82AA915F6>