Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Feb 2012 13:24:42 -0600
From:      Zhihao Yuan <lichray@gmail.com>
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:  <CAGsORuBjScOG3V1BykyELtqQhvzk-mKELoVrdUEfOk3Zh4X56w@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 Fri, Feb 17, 2012 at 7:59 AM, Mikhail T. <mi+thun@aldan.algebra.com> wro=
te:
> 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 i=
n
> LIB_DEPENDS.

I regard this as a wrong practice. Here is why:

1. The way you specify the version in LIB_DEPENDS has NO relation with
how the port link to the lib. The port can link to the major version
(pkg-config), or the .so, etc.

2. One responsibility of the ports system is to protect the user from
suffering from running a software which links to a ABI incompatible,
hence, wrong shared library. A software runs incorrectly is a
disaster, and the shared library version is to prevent this, and the
ports system is to protect the versioned shared libraries. Thus -- A
port fails to find its depends better than it does not link, a
software does not link is better than it does not run correctly. And
your practice is trying to remove such protection.

3. "Known to cause problem"? Can I infer ""you can predict the future"
from that?

So, to link to a version explicitly should be the default. Only a
library behaviors "good" in its development history can be considered
to use it's libname only in LIB_DEPENDS.

>
> =C2=A0 -mi
>
>
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"



--=20
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___________________________________________________
4BSD -- http://4bsd.biz/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGsORuBjScOG3V1BykyELtqQhvzk-mKELoVrdUEfOk3Zh4X56w>