From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-30913-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 12312 invoked by alias); 18 Dec 2012 16:30:18 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 30913
Received: (qmail 15043 invoked from network); 18 Dec 2012 16:30:11 -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
Received-SPF: none (ns1.primenet.com.au: domain at ckhb.org does not designate permitted sender hosts)
Date: Tue, 18 Dec 2012 08:22:58 -0800 (PST)
From: "S. Cowles" <scowles@ckhb.org>
X-X-Sender: picmar@ckhb01
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: It's time for 5.0.1
In-Reply-To: <20121216200356.76fd2f4d@pws-pc.ntlworld.com>
Message-ID: <alpine.DEB.2.02.1212180758190.23648@ckhb01>
References: <20121206194404.698168c9@pws-pc.ntlworld.com> <121208115416.ZM27266@torch.brasslantern.com> <20121216200356.76fd2f4d@pws-pc.ntlworld.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
X-Face: Ek1c-Ll9]E|9mF*Z|hf5VSHqF.]0Qv%;h%=Zne"Y3am*(:Tf_BlXI;j'}FMhu%sNCjSk|</(~~v,k&/W^J;>cxD~oD:g5Tv,gN}{Y8("m<8<%%=_vy
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Sun, 16 Dec 2012, Peter Stephenson wrote:

> I've uploaded zsh-5.0.0-test-1 to ftp.zsh.org in the zsh/development
> directory.  If you get a chance please see if there's anything wrong
> with this before I release 5.0.1.

Compile and link are fine on osx mountain lion (12.2.0) with homebrew, and ubu
12.04 32bit and 64bit.

I did run into an install problem that I have never encountered before; if it is
documented and I missed it, I apologize for the noise.

Just recently, I have begun running with a umask of 0077.  So, when the install
procedure creates new directories, the mode of the new dirs is 0077.  Since I install
as root, this creates the obvious suite of problems when running as a regular user:
permission denied errors for various shared libraries and functions (e.g. vcs_info).
To fix the install, I clean house and build from a zsh-clean environment with a
umask of 0022.

My current workaround is to force the umask to 0022 during build and install.  Would
it be appropriate to put mode setting code into mkinstalldirs?