Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 May 2015 13:46:12 -0400
From:      "Mikhail T." <mi+thun@aldan.algebra.com>
To:        Bryan Drewery <bdrewery@FreeBSD.org>, ports-committers@freebsd.org,  svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r387637 - in head/devel/tcllib: . files
Message-ID:  <556602E4.9020106@aldan.algebra.com>
In-Reply-To: <55660165.3050106@FreeBSD.org>
References:  <201505271719.t4RHJXY6010274@svn.freebsd.org> <55660165.3050106@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 27.05.2015 13:39, Bryan Drewery wrote:
>> +lib/tcllib/tcllibc/%%BINARCH%%/tcllibc.so
> Bundling libraries is bad.
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/bundled-libs.html
>From the link:

    Some software requires the porter to locate third-party libraries and add
    the required dependencies to the port. Other software bundles all necessary
    libraries into the distribution file.

This is not, what is happening here. The tcllibc.so contains the compiled
implementations of the tcllib's modules.
> It will also confuse pkg unless BUNDLE_LIBS=yes is added.
>
> Can tcllib not use critcl from its own package?
Critcl port does not install binaries. "critcl" and "tcllibc" are different
things -- the former helps out with compiling C-code, the latter is a result of
such compilation. Yours,

    -mi




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