From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: MacOS X patches
Date: Tue, 04 Nov 2014 20:04:47 -0800 [thread overview]
Message-ID: <141104200447.ZM1399@torch.brasslantern.com> (raw)
In-Reply-To: <CAHYJk3Q5mxAaxBWNfqQi5QNvL=S3Th1MnQtkRysDhfDmkp7mFA@mail.gmail.com>
On Nov 1, 8:57am, Mikael Magnusson wrote:
} Subject: Re: MacOS X patches
}
} On Sat, Nov 1, 2014 at 5:48 AM, Pedro Giffuni <pfg@freebsd.org> wrote:
} >
} > http://www.opensource.apple.com/source/zsh/zsh-61/patches/
}
} I wonder what they have against the calendar system documentation.
I suspect they removed it because they don't install the corresponding
functions ... because they want everyone to use their calendar manager?
"ls $fpath/calendar(N)" finds nothing.
} The only "interesting" patch I can see is the utmpx one
Yeah, I'm a bit curious about that one. If that's really necessary, how
does zsh even compile without it? Does something get "configure"d away?
} I'm not exactly sure what the arg_zero patch does though.
Apparently it's somehow possible to invoke the program with argc == 0.
The call to zerr() eventually goes through zwarning() which passes
argzero to nicezputs(), so it has to have a value for that to work.
But isn't the real bug that something runs the shell with argv empty?
} (One wonders why they want to modify the
} install-strip target instead of just calling the install target).
Probably just preventing someone from trying something that's going
to fail anyway.
The no_auto.patch and config.h.ed bits appear to have something to do
with compiling from the tarball. I'm guessing config.h.ed is run to
undo something that configure gets "wrong," and then that makes the
default build want to re-run autoconf/autoheader for dependencies.
next prev parent reply other threads:[~2014-11-05 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 4:48 Pedro Giffuni
2014-11-01 7:57 ` Mikael Magnusson
2014-11-05 4:04 ` Bart Schaefer [this message]
2014-11-05 16:56 ` 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=141104200447.ZM1399@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).