zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Module config
Date: Tue, 5 Dec 2000 22:54:22 +0300	[thread overview]
Message-ID: <000901c05ef5$46435470$c9c9ca95@mw1g666c> (raw)
In-Reply-To: <0G53006KTSR1X9@la-la.cambridgesiliconradio.com>


One more remaining part is documentation. It looks sensible to omit docs for
those modules that are not built. I've tried to do it and failed. There are
at least two problems:

- minor: zftpsys.yo is built as part of "main" documentation. It logically
should be built together with mod_zftp. Also, several builtins that are now
in modules are listed in main documentation (e.g. limit).

- major: list of modules to build is created dynamically when you run make;
it is impossible to build list of modules at configure time.

Hence the question: is there any reason we generate module list and
makefiles at compile time? Autoconf allows you to run any command(s) as part
of config.status - we can as easily call mkmakemod & Co. as part of (and
move current creation of config.modules into) config.status.

Should make the whole story more simple.

-andrej


  reply	other threads:[~2000-12-05 19:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 18:28 PATCH: function install Peter Stephenson
2000-12-02 23:37 ` Bart Schaefer
2000-12-04 10:47   ` Peter Stephenson
2000-12-04 19:12     ` Peter Stephenson
2000-12-05 15:18 ` Module config Andrej Borsenkow
2000-12-05 16:35   ` Peter Stephenson
2000-12-05 19:54     ` Andrej Borsenkow [this message]
2000-12-06 10:41       ` Peter Stephenson

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='000901c05ef5$46435470$c9c9ca95@mw1g666c' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.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).