From owner-freebsd-ports@FreeBSD.ORG Sun Sep 2 17:16:34 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D42E516A418 for ; Sun, 2 Sep 2007 17:16:34 +0000 (UTC) (envelope-from gamato@users.sf.net) Received: from slimak.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.freebsd.org (Postfix) with SMTP id 4743F13C458 for ; Sun, 2 Sep 2007 17:16:34 +0000 (UTC) (envelope-from gamato@users.sf.net) Received: (qmail 41259 invoked by uid 0); 2 Sep 2007 16:49:51 -0000 Received: from r5j156.net.upc.cz (HELO ?86.49.9.156?) (86.49.9.156) by smtp.dkm.cz with SMTP; 2 Sep 2007 16:49:51 -0000 Message-ID: <46DAE9AF.8020706@users.sf.net> Date: Sun, 02 Sep 2007 18:49:51 +0200 From: mato User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.6) Gecko/20070821 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Kris Kennaway References: <20070830004020.GA58539@blazingdot.com> <46DA98A3.5030204@FreeBSD.org> In-Reply-To: <46DA98A3.5030204@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: ports system and umask X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2007 17:16:34 -0000 Kris Kennaway wrote: > martinko wrote: >> Hallo, >> >> We have similar problems here -- default umask is set to 027 and >> therefore one needs to always remember changing it to 022 prior >> installing any ports or packages. >> Been bitten many times because of this. :-\ >> >> Martin > > There is an argument that if you set the umask then you are getting > exactly what you ask for :) > > Kris Yes, you're right, and it works for us and I can imagine many situations people change default umask. But IMHO it doesn't make sense for ports/packages as installing them with non-default umask effectively renders them unusable. Therefore it seems to me that either ignoring umask or at least warning people umask is changed would be correct in this case. Martin