From owner-freebsd-ports@FreeBSD.ORG Sat Oct 12 13:44:13 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 37E15BBD; Sat, 12 Oct 2013 13:44:13 +0000 (UTC) Date: Sat, 12 Oct 2013 13:44:13 +0000 From: Alexey Dokuchaev To: Matthew Seaman Subject: Re: How to disable staging support in ports tree universally? Message-ID: <20131012134413.GA35617@FreeBSD.org> References: <20131012055953.GA4352@icarus.home.lan> <5259051D.7060205@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5259051D.7060205@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 13:44:13 -0000 On Sat, Oct 12, 2013 at 09:15:25AM +0100, Matthew Seaman wrote: > Yes, there are a lot of changes happening at the moment. We're trying > to catch up with ten or more years of progress in a year or so. The > technical reasoning behind our implementing these changes has been > discussed elsewhere so I'll not rehash it further here other than to say > that the vast majority of ports users and developers are behind where > we're going with this. One of the most annoying things about staging (for me) is that it broke many ports "make install" from regular user. E.g. audio/faad and misc/mc are affected, just to name a few. At a glance, it happens because they first install files with 444 perms, and then try to do something on them. Previously it was done after su(1) had asked for root, but with staging, it's done as user, and thus fails. ./danfe