From owner-freebsd-questions Mon Nov 22 9:22:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B033B14C0A for ; Mon, 22 Nov 1999 09:22:35 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id JAA28318; Mon, 22 Nov 1999 09:48:58 -0800 (PST) Date: Mon, 22 Nov 1999 09:48:58 -0800 (PST) From: Alfred Perlstein To: Kresimir Kumericki Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Permissions of /usr/ports ? In-Reply-To: <19991122181345.A11464@phy.hr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Kresimir Kumericki wrote: > When installing new packages on Unices I usually follow > the procedure where I do all the preparatory work (fetching, > applying patches, playing with configuration, building > the executable, testing) as nonprivileged user and only do "make > install" as root. (BTW, I do "make -n install" first.) > Now, I cannot do that with FreeBSD ports because nonprivileged > users don't have write permission on /usr/ports . What do > you people do? Do everything as root? > If I made /usr/ports/* writable by some other user or group > I presume that that would interfere with updating the ports via > cvsup. > Any suggestions or comments? chown the ports tree to your port-meister account, and have him do the cvsup's instead of as root. he should be able to build programs in the tree and you'll still be able to su to install. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message