From owner-freebsd-ports@FreeBSD.ORG Mon Apr 26 04:55:57 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B89A5106564A for ; Mon, 26 Apr 2010 04:55:57 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4951A8FC19 for ; Mon, 26 Apr 2010 04:55:56 +0000 (UTC) Received: (qmail 31039 invoked by uid 399); 26 Apr 2010 04:55:55 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 26 Apr 2010 04:55:55 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BD51CD5.9040304@FreeBSD.org> Date: Sun, 25 Apr 2010 21:55:49 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Eitan Adler References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: feature request for portmaster: check for permissions on --check-depends and friends 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: Mon, 26 Apr 2010 04:55:57 -0000 On 04/25/10 12:03, Eitan Adler wrote: > When I run portmaster with --check-depends or --check-port-dbdir as a > non-root user portmaster will continue to attempt to write to the db > dir. > For example > ===>>> Checking jpeg-8_1 > ===>>> Updating +REQUIRED_BY > install: /var/db/pkg/jpeg-8_1/+REQUIRED_BY: Permission denied > > portmaster should check before it goes through the whole process and > see if it has write access to /var/db/ports. I'm sort of ambivalent about this. For the most part I would imagine that users would either anticipate this issue and run it as root or set up PM_SU_CMD. OTOH, I could imagine users might want to do things like this that require root access to actually change things as a regular user first as a painless way to see what would happen if they ran the command as root. This is the first time this issue has come up, what do others think? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/