From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23352 invoked by alias); 5 Nov 2014 04:05:00 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33602 Received: (qmail 15980 invoked from network); 5 Nov 2014 04:04:49 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=HrPBwPXX c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=6I5d2MoRAAAA:8 a=t-IPkPogAAAA:8 a=qXULy_tJNFPtoazfCNgA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141104200447.ZM1399@torch.brasslantern.com> Date: Tue, 04 Nov 2014 20:04:47 -0800 In-reply-to: Comments: In reply to Mikael Magnusson "Re: MacOS X patches" (Nov 1, 8:57am) References: <8123AE4B-66A3-4789-B0A3-5E5C26DB986D@freebsd.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh workers Subject: Re: MacOS X patches MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 1, 8:57am, Mikael Magnusson wrote: } Subject: Re: MacOS X patches } } On Sat, Nov 1, 2014 at 5:48 AM, Pedro Giffuni 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.