From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 09:53:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6D9716A41F for ; Fri, 30 Dec 2005 09:53:21 +0000 (GMT) (envelope-from andrea@acampi.hq.inet.it) Received: from acampi.hq.inet.it (out-11.hq.inet.it [194.185.62.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DA5543D60 for ; Fri, 30 Dec 2005 09:53:20 +0000 (GMT) (envelope-from andrea@acampi.hq.inet.it) Received: by acampi.hq.inet.it (Postfix, from userid 1000) id 6BC613D; Fri, 30 Dec 2005 10:53:19 +0100 (CET) Date: Fri, 30 Dec 2005 10:53:19 +0100 From: Andrea Campi To: Matthew Seaman Message-ID: <20051230095318.GX1779@webcom.it> References: <20051229193328.A13367@cons.org> <20051230021602.GA9026@pit.databus.com> <43B498DF.4050204@cyberwang.net> <43B49B22.7040307@gmail.com> <20051229220403.A16743@cons.org> <20051230053906.GA75942@pit.databus.com> <2440.193.68.33.1.1135932286.squirrel@193.68.33.1> <86irt7dk5k.fsf@xps.des.no> <43B4FFB2.4090203@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43B4FFB2.4090203@infracaninophile.co.uk> User-Agent: Mutt/1.5.11 Cc: Dag-Erling Sm?rgrav , freebsd-current@freebsd.org, ?d?m Szilveszter Subject: Re: fetch extension - use local filename from content-disposition header X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 09:53:22 -0000 On Fri, Dec 30, 2005 at 09:36:50AM +0000, Matthew Seaman wrote: > Not if you, as a naive user, take a freshly installed system and an > unmodified environment. You'll need to make a bunch of changes > before everything will run smoothly: > > * Make /usr/ports/distfiles writable by user or set $DISTDIR to > a writable directory Right... > * Make /var/db/ports writable by user or set $PORT_DBDIR to a > writable location Eww... > * Make each port directory writable -- so the the 'work' directories > can be created -- or set $WRKDIRPREFIX to a writable location. Right... > And in fact, if you go on to do the same deal with $PKG_DBDIR and $PREFIX > plus set $INSTALL_AS_USER then you can install most ports entirely as a > mortal user -- the exceptions being ports that want to run mtree(8) or that > need to install programs with specific UID or GIDs. Well, this MIGHT work for a single user system, but it's hackish and really dangerous... > Not setting $INSTALL_AS_USER means you'll be prompted to supply the root > password where needed at install time. Not if you use sudo. The ports mk have a know to specify what to use in place of su, and it works nicely. Now you get prompter only when the (user configurable) timeout expires. Much, much better. I'd even go so far as suggesting sudo in the base system, since it's the first thing many people install from ports AND it's such a pain to upgrade using portupgrade... Bye, Andrea -- Press every key to continue.