From owner-freebsd-stable Fri Aug 23 5:50:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C78037B400 for ; Fri, 23 Aug 2002 05:50:23 -0700 (PDT) Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4988243E77 for ; Fri, 23 Aug 2002 05:50:22 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [IPv6:::1]) by lurza.secnetix.de (8.12.5/8.12.5) with ESMTP id g7NCoJmC073805 for ; Fri, 23 Aug 2002 14:50:19 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.5/8.12.5/Submit) id g7NCoJQ3073804; Fri, 23 Aug 2002 14:50:19 +0200 (CEST) Date: Fri, 23 Aug 2002 14:50:19 +0200 (CEST) Message-Id: <200208231250.g7NCoJQ3073804@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: ports problems -- FIXED In-Reply-To: <20020822114419.G43401@ffwd.cx> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.6-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Skye Poier wrote: > completely non-intuitive mistake? Its not even a mistake really, > show me a man page or a handbook entry where it says "don't put trailing > slashes in your path".. There's no manpage either that tells you not to shot yourself in the foot. The $PATH is a sequence of dirctory names (separated by colons). A directory name is just that -- the file name of a directory. Such a name _never_ ends with a slash, because the slash is used to separate components of a path. Of course, according to RFC1123 ("be liberal in what you accept"), programs should be forgiving about such mistakes and ignore the trailing slash. After all, it's clear what the user actually meant. But on the other hand, that behaviour encourages such mistakes. As you said, you've had it in your .tcshrc for years without noticing. I agree with Lowell that you should fix the statement in your .tcshrc. Changing the bsd.mk file, libtool or tcsh would fix it for you in this particular case, but you might stumble across another script next week which assumes no trailing slashes in $PATH. Therefore, fixing it once and for all in your .tcshrc is the right thing. Regards Oliver PS: Just to make sure: My e-mail message is in no way meant to be offensive or insulting. I'm just trying to express my own technical opinion about this matter. PPS (for the irony-impaired): The first sentence was a joke. -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message