From: ZyX <kp-pav@yandex.ru>
To: Peter Stephenson <p.stephenson@samsung.com>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Zpython inclusion
Date: Mon, 02 Feb 2015 22:34:15 +0300 [thread overview]
Message-ID: <20975221422905655@web8j.yandex.ru> (raw)
02.02.2015, 20:34, "Peter Stephenson" <p.stephenson@samsung.com>:
> On Mon, 2 Feb 2015 08:18:29 +0300
> ZyX <kp-pav@yandex.ru> wrote:
>> if you want to consider merging https://bitbucket.org/ZyX_I/zpython I
>> can convert it back to a patch it used to be once. I introduced it to
>> a list, but it did not get much attention.
>
> It's clearly a useful addition but I think it would be better to keep it
> out of the main source to avoid making that depend (even optionally) on
> Python; this is potentially complex for people who don't need it and
> subject to change in ways not necessarily tied to changes in zsh, and we
> have enough maintenance headaches in the main code that it's nice to
> have something that actually does work as an add-on :-)
The big problem with zpython is that nobody is actually providing the necessary headers. I only saw [zsh-dev][1] package in debian-based distribution, but I failed to find any deb-src package which depends on it. The issue with this package is that it installs copied zsh headers, but `zsh.h` is quite useless without defines from `config.h`; I wanted to see how they cope with the problem.
I can live with a custom zsh ebuild. I can probably push changes to the Gentoo upstream (have not actually tried, but I guess I need to). But I can’t fix all the other distributions. Currently zpython provides an option to build itself using zsh built in its own repository which should be convenient enough for packaging (in any case zsh needs to be built first) in binary distributions, but not for users willing to compile it themselves (no usable headers out there) or source-based distributions.
Using separate repository just for zpython was chosen because I neither like constant rebasing nor constant merging with upstream; I used to perform the former prior to that.
[1]: https://packages.debian.org/search?keywords=zsh-dev&searchon=names&exact=1&suite=all§ion=all
>
> It would be sensible to provide pointers in the main distribution,
> though.
>
> pws
next reply other threads:[~2015-02-02 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 19:34 ZyX [this message]
2015-02-03 12:56 ` Axel Beckert
2015-02-03 16:24 ` ZyX
2015-02-03 16:28 ` ZyX
2015-02-03 16:36 ` Axel Beckert
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=20975221422905655@web8j.yandex.ru \
--to=kp-pav@yandex.ru \
--cc=p.stephenson@samsung.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).