From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Adding (compiling) a module to already build Zsh
Date: Wed, 14 Sep 2016 09:16:37 +0200 [thread overview]
Message-ID: <CAKc7PVCy4R=Frg1FH_iBaT-BiWiO13p27VDyPX_x9AkT9rCX0w@mail.gmail.com> (raw)
In-Reply-To: <160912103839.ZM25202@torch.brasslantern.com>
On 12 September 2016 at 19:38, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 12, 8:12am, Sebastian Gniazdowski wrote:
> }
> } on IRC someone asked how to "add gdbm". I wonder if the module can be
> } easily added to already installed Zsh, if it's not already bundled?
>
> It should be possible to do this provided that
> (a) the zsh source matching the installed binary is available to
> compile against and
Could be something like the commonly occurring package
kernel-headers-*.(deb|rpm|etc.) created, with mostly header files
constituting a build environment (source files are rather not needed?)
? It would be cool thing from one other reason. For example, there is
gdbm module for Zsh. Its features make it capable of rising Zsh code
to another level. However, it is rarely available in distributed Zsh
packages (licensing issue? I'm not sure if license issue doesn't apply
only to pcre module). However, with easily available build environment
one would be able to distribute a gdbm module together with his plugin
and this way overcome licensing issue.
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-09-14 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:12 Sebastian Gniazdowski
2016-09-12 17:38 ` Bart Schaefer
2016-09-14 7:16 ` Sebastian Gniazdowski [this message]
2016-09-14 8:54 ` Oliver Kiddle
2016-09-14 16:19 ` Bart Schaefer
2016-09-14 19:03 ` Mikael Magnusson
2016-09-15 12:22 ` Sebastian Gniazdowski
2016-09-14 15:09 ` Lawrence Velázquez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKc7PVCy4R=Frg1FH_iBaT-BiWiO13p27VDyPX_x9AkT9rCX0w@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).