zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: omit modules from compilation and installation process
Date: Mon, 14 Feb 2000 19:10:04 +0000	[thread overview]
Message-ID: <E12KQpH-0006cW-00.2000-02-14-19-06-28@cmailg2.svr.pol.co.uk> (raw)
In-Reply-To: ""Andrej Borsenkow""'s message of "Mon, 14 Feb 2000 10:14:11 +0300." <000001bf76bb$174c9500$21c9ca95@mow.siemens.ru>

"Andrej Borsenkow" wrote:
> > Now you can give configure a comma-separated list of modules not
> > to compile
> > nor install as --enable-omit-modules=zsh/example,zsh/zpty.  Having to use
> > the `enable' in front is a bit tacky, but as far as I can see there's no
> > way round it.
> 
> Ahem ... what's wrong with --(disable|enable)-modules=... ?

--disable-modules is a synonym for --enable-modules=no, it doesn't take
arguments.  The nearest possibility is Bart's suggestion for using some
kind of negation symbol.

> Is it usable for static compilation as well?  Will it completely replace
> defaults? Probably, meta keywords like
> 
> --enable-modules=all
> --enable-modules=default,zsh/zpty
> 
> would be useful (but, may be, for static case only).

The first question is what Bart was addressing.  Something along those
lines should presumably be possible, but I think it might be a bit
confusing to overload just the one switch.  I might suggest keeping
--enable-omit-modules as it is and having --enable-builtin-modules=... to do
what you (and Bart) are suggesting.  Then it ought to be possible to have
"all" (build in all the modules there are, phew), and possible "default"
in the manner you suggest.  This is a little harder than
--enable-omit-modules, but probably not too bad.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>


  reply	other threads:[~2000-02-14 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-13 18:44 Peter Stephenson
2000-02-14  1:16 ` Bart Schaefer
2000-02-14  7:14 ` Andrej Borsenkow
2000-02-14 19:10   ` Peter Stephenson [this message]
2000-02-14 10:11 ` Zefram

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=E12KQpH-0006cW-00.2000-02-14-19-06-28@cmailg2.svr.pol.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --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).