Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Jan 2020 05:59:13 +0000
From:      Alexey Dokuchaev <danfe@freebsd.org>
To:        Baptiste Daroussin <bapt@freebsd.org>
Cc:        Yuri <yuri@rawbw.com>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r522202 - in head/audio: . libaudec libaudec/files
Message-ID:  <20200106055913.GA44473@FreeBSD.org>
In-Reply-To: <20200106055041.lggeghkulpm32g3w@ivaldir.net>
References:  <202001060451.0064pfdH044874@repo.freebsd.org> <20200106052719.5oqlohpaadoua3hp@ivaldir.net> <181b91d7-f2dc-750b-a65c-840241aef5b6@rawbw.com> <20200106055041.lggeghkulpm32g3w@ivaldir.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 06, 2020 at 06:50:41AM +0100, Baptiste Daroussin wrote:
> On Sun, Jan 05, 2020 at 09:42:23PM -0800, Yuri wrote:
> > On 2020-01-05 21:27, Baptiste Daroussin wrote:
> > > It is also a good practice to have a soname for shared library in
> > > general. (A soname which is not the name of the .so file itself)
> > 
> > I know, but they didn't assign a soname.

You might want to see r423146 as an example[1].

> It is up to the committer to ensure what is packaged is properly packaged,
> so if upstream does not provide a SONAME, you should patch the build
> system to provide one before adding to the ports tree.

Did we ever document this in the PHB?  I've found the link above in the
2016 discussion[2] which says that back in those time it had no match for
SONAME, had this changed since then?

./danfe

[1] https://svnweb.freebsd.org/ports?view=revision&revision=423146
[2] https://lists.freebsd.org/pipermail/freebsd-ports/2016-October/105114.html



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