Date: Fri, 17 Feb 2012 17:36:58 +0000 From: Chris Rees <crees@freebsd.org> To: "Mikhail T." <mi+thun@aldan.algebra.com> Cc: Jakub Lach <jakub_lach@mailplus.pl>, freebsd-ports@freebsd.org Subject: Re: Re: recent portrevision bump for libvpx Message-ID: <CADLo83_ytDv2%2BKER5q9CF2y_T03PTegpArZ_PX0i-Lnnjtbd5Q@mail.gmail.com> In-Reply-To: <4F3E5D41.9050503@aldan.algebra.com> References: <4F3E289D.9050605@FreeBSD.org> <4F3E2CED.90601@FreeBSD.org> <4F3E3537.9040105@FreeBSD.org> <1329478316415-5492205.post@n5.nabble.com> <4F3E5D41.9050503@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 February 2012 13:59, Mikhail T. <mi+thun@aldan.algebra.com> wrote: > On -10.01.-28163 14:59, Jakub Lach wrote: >> >> Speaking of recent libvpx update, some ports explicitly look >> for libvpx.so.0, and fail to update trying to install again libvpx >> which is already installed. >> >> e.g. multimedia/gstreamer-plugins-vp8 > > Yet again I'd like to point out, that -- contrary to the wide-spread > practice -- ports should not, by default, list a particular shlib major > number in LIB_DEPENDS. Only in cases, when a wrong version of some libfoo is > known to cause problems, should the correct version be explicitly given in > LIB_DEPENDS. Perhaps someone could make a patch for the Porter's Handbook. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_ytDv2%2BKER5q9CF2y_T03PTegpArZ_PX0i-Lnnjtbd5Q>