From owner-freebsd-ports@FreeBSD.ORG Mon Jan 31 15:06:25 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6771216A4CE for ; Mon, 31 Jan 2005 15:06:25 +0000 (GMT) Received: from mail.seekingfire.com (caliban.rospa.ca [24.72.10.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id 084AE43D2D for ; Mon, 31 Jan 2005 15:06:25 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 63FCA4F6; Mon, 31 Jan 2005 09:06:24 -0600 (CST) Date: Mon, 31 Jan 2005 09:06:24 -0600 From: Tillman Hodgson To: FreeBSD-Ports Message-ID: <20050131150624.GO9276@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does X-No-prize-winner: Nathanael User-Agent: Mutt/1.5.6i Subject: Ports foot-shooting revealed! (learning the hard way ...) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 15:06:25 -0000 Howdy folks, This isn't a rant, because I'd have to rant about my own stupidity. Instead it's more of a humourous story about what /not/ to do. Anyway, I was poking around for a port a few days ago, so I did this: # cd /usr/ports # make seach name="tor" make: don't know how to make seach. Stop Gah. I do that all the time. It's like my fingers sometimes don't hit the 'r' key hard enough. (Yes, this is part of the foot-shooting story). Ok, here we go again: # make search name="^tor" (Much better, output is a bunch of results instead of an error) Oh, hey /usr/ports/security/tor looks like what I was thinking of! # cd /usr/pots/security/tor bash: cd: usr/pots/security/tor: No such file or directory (I didn't notice this -- typing too fast) # make install (starts to build *all* ports in the ports tree ...) (I wander off for some coffee, thinking all is right with the world) I can't think of any reason why anyone would want to build *all* ports, especially considering that some of them would conflict with each other. So I don't think that this command would even work (given enough time, CPU and disk space). I was certainly surprised the first time I did it. In some ways it reminds me the "rm -rf / shouldn't work" bike shed from a few months ago. Checking for PWD=/usr/ports would be the same bike shed, I suspect. Granted, it could be easily solved by smarter shell usage. For example, I could have done `cd /usr/pots/security/tor && make install` (my new preferred "watch out for typos!" method). Or I could have actually waited a second before typing `make install` and *read* the error message. Practiced safe "root" and all that. But I didn't. Twice now, in the past few years. I generally notice about the time that I think "Hmmmm, that port shouldn't be taking *that* long to build ...". The cleanup isn't too hard: the dates from the /var/db/ stuff are very helpful. But it's annoying :-) Ah well, hopefully someone will learn from me revealing my foot-shooting to the world and avoid a similar fate ;-) -T -- The strictest limits are self-imposed. - Friedre Ginaz, Philosophy of the Swordmaster