From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Oliver Kiddle <opk@u.genie.co.uk>, zsh-workers@sunsite.dk
Subject: Re: PATCH: zsh/pcre module
Date: Tue, 3 Jul 2001 17:21:53 +0000 [thread overview]
Message-ID: <1010703172154.ZM14855@candle.brasslantern.com> (raw)
In-Reply-To: <3B41F8ED.9892E7F6@u.genie.co.uk>
On Jul 3, 5:55pm, Oliver Kiddle wrote:
} Subject: Re: PATCH: zsh/pcre module
}
} How easy is it to package up modules separately in such a way that they
} could be built and installed without needing to be unpacked over the zsh
} source and compiled with it.
Not very easy, unfortunately. The zsh.mdh file includes all the .epro
files, which are generated during the zsh build and may differ among
operating systems.
} Ideally, we would have a set of include
} files which was all anyone needed to build a separate zsh module.
That could work, but only for modules that didn't need to reference any
of the external symbols other than addbuiltin() etc. That's a pretty
small subset of the current crop of modules.
} Does anyone remember what happened to the perl module someone posted
} quite a while back?
The URL was
http://www.phydeaux.org/perl/zperl-0.01.patch.gz
I haven't looked to see if it's still there.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-03 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 19:35 Clint Adams
2001-07-02 23:10 ` Bart Schaefer
2001-07-03 5:54 ` Andrej Borsenkow
2001-07-03 6:25 ` Bart Schaefer
2001-07-03 6:30 ` Andrej Borsenkow
2001-07-03 16:32 ` Bart Schaefer
2001-07-03 16:35 ` Clint Adams
2001-07-03 16:55 ` Oliver Kiddle
2001-07-03 16:59 ` Clint Adams
2001-07-03 17:19 ` Andrej Borsenkow
2001-07-03 17:18 ` Andrej Borsenkow
2001-07-03 17:21 ` Bart Schaefer [this message]
2001-07-03 17:43 ` Clint Adams
2001-07-17 16:28 ` Fletch
2001-07-03 6:57 ` Andrej Borsenkow
2001-07-03 16:21 ` Clint Adams
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=1010703172154.ZM14855@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.dk \
/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).