Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Nov 1999 15:38:22 -0500 (EST)
From:      James Gill <gill@topsecret.net>
To:        Alfred Perlstein <bright@wintelcom.net>
Cc:        Kresimir Kumericki <kkumer@phy.hr>, freebsd-questions@FreeBSD.ORG
Subject:   Re: Permissions of /usr/ports ?
Message-ID:  <Pine.BSF.4.10.9911221537040.3273-100000@pacific.int.topsecret.net>
In-Reply-To: <Pine.BSF.4.21.9911220947060.4557-100000@fw.wintelcom.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Nov 1999, Alfred Perlstein wrote:
->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.)

Why would one configure the ports area to be tinkerable by a nonprivledged
user?

->>   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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911221537040.3273-100000>