Re: Can be a module linked to library to which Zsh isn't linked?

[Sebastian Gniazdowski <sgniazdowski@gmail.com>]

On 3 October 2015 at 20:55, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Oct 3,  4:24pm, Sebastian Gniazdowski wrote:
> } Modules gdbm and pcre aren't built by default and they make
> } zsh binary linked to libgdbm, libpcre. I thought that's why they
> } aren't build by default - because they add dependencies to zsh binary
>
> It's because they add *licensing* dependencies, IIRC, not because they
> add shared-object dependencies.

The shared-object dependencies can also be a problem. Uninstalling
libpcre could yield zsh unworking. Having modified LIBS for pcre, gdbm
modules would solve this. Packagers would build such modules instead
of leaving them inactive. However for those two the licensing aspect
overlaps as you wrote, so it's a lost battle for them anyway (BTW
libpcre is BSD, isn't it compatible with Zsh?).

What bothers me is that someone who builds zsh against termcap or
terminfo loses curses module. Having a bit of separate tests in
configure against libraries needed by modules but not zsh itself would
solve this. Is Zsh open for such change?

Best regards,
Sebastian Gniazdowski