From: Bart Schaefer <schaefer@brasslantern.com>
To: Adam Spiers <adam@spiers.net>, zsh-workers@sunsite.dk
Subject: Re: /usr/local/bin/perl
Date: Thu, 16 Aug 2001 20:52:42 +0000 [thread overview]
Message-ID: <1010816205242.ZM12361@candle.brasslantern.com> (raw)
In-Reply-To: <20010816151235.B20958@thelonious.new.ox.ac.uk>
On Aug 16, 3:12pm, Adam Spiers wrote:
} Subject: Re: /usr/local/bin/perl
}
} > } If we use configure, presumably that would mean having (say)
} > } Utils/helpfiles auto-generated from Utils/helpfiles.in? My vote is
} > } for that option.
} >
} > Yes, that would be it, but my vote is still to avoid mucking with this
} > in configure. Maybe something like the following, run through the
} > just-compiled zsh?
}
} I suppose that's fine, as long as it wouldn't mess things up if you
} ran it twice. I still slightly prefer going via configure, as that
} way you're not altering CVS files. You probably have a more
} convincing argument the other way though :-)
Strangely enough, I don't, or at least not directly.
I just think it's a waste of effort. None of those files actually gets
installed anywhere (except the two in Functions/Misc, and they really
are meant to be shell functions and shouldn't have a #! line at all,
nor should "reporter" for that matter). If they *were* installed, I'd
recommend fixing the #! as part of the installation process; but they
aren't, so there's no reason to have a separate (and nonfunctional)
"source" file as well as a "compiled" one.
So I'm willing to bend a little and provide a way for you to fix them
up if you want to install them yourself, but I don't want more clutter
in the source tree and the configure script if we aren't going to make
installing them a part of the regular build process.
Even if there were separate source and compiled files, I still wouldn't
want to do it with configure. A "make"-time transformation with a little
script like the one I supplied would be sufficient.
(Looking back at your original message, I'm curious how Util/helpfiles
manages to appear twice with two different #! lines.)
--
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-08-16 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 13:28 /usr/local/bin/perl Adam Spiers
2001-03-27 15:17 ` /usr/local/bin/perl Oliver Kiddle
2001-08-15 14:54 ` /usr/local/bin/perl Adam Spiers
2001-08-15 16:59 ` /usr/local/bin/perl Bart Schaefer
2001-08-16 14:12 ` /usr/local/bin/perl Adam Spiers
2001-08-16 20:52 ` Bart Schaefer [this message]
2001-03-27 18:19 ` /usr/local/bin/perl Bart Schaefer
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=1010816205242.ZM12361@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=adam@spiers.net \
--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).