zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Module system RE: 3.1.9-dev-6
Date: Mon, 04 Sep 2000 16:01:18 +0100	[thread overview]
Message-ID: <0G0D00FGZB2697@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Mon, 04 Sep 2000 18:23:21 +0400." <000101c0167b$ad951130$21c9ca95@mow.siemens.ru>

> Add single parameter
> 
> --enable-zsh-modules="module list"

I came to the conclusion we had come to the limit of what we could easily
do with configure:  it's extremely uncomfortable for anything complicated,
and we keep getting requests for things that configure can't do.  It's
extremely hard to upgrade; the code is spread all over, the configure
options interact, and the active code is somewhere else entirely.  It's
hard to set up:  you end up fiddling with command line options and
rerunning configure.  Furthermore, it's horrible to write in comparison
with a shell-script-based system.  So I would like to remove the module
control stuff (which has appeared in the last couple of 3.1 releases) from
configure and do it as suggested --- set up a file based on the modules
that exist, and allow the installer to edit it.

The subtext is, if people would prefer a purely configure-based system it's
unlikely to be me that gets around to writing it any time in the
foreseeable future.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2000-09-04 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-04 14:07 3.1.9-dev-6 Peter Stephenson
2000-09-04 14:23 ` Module system 3.1.9-dev-6 Andrej Borsenkow
2000-09-04 15:01   ` Peter Stephenson [this message]
2000-09-06  9:29 ` 3.1.9-dev-6 Andrej Borsenkow

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=0G0D00FGZB2697@la-la.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --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).