From owner-freebsd-hackers  Mon Sep 25 21:19:38 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA10697
          for hackers-outgoing; Mon, 25 Sep 1995 21:19:38 -0700
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA10692
          for <hackers@freebsd.org>; Mon, 25 Sep 1995 21:19:34 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA19471
  (5.67a/IDA-1.5 for hackers@freebsd.org); Mon, 25 Sep 1995 22:57:55 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id WAA27631 for hackers@freebsd.org; Mon, 25 Sep 1995 22:49:34 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509260349.WAA27631@bonkers.taronga.com>
Subject: Re: ports startup scripts
To: hackers@freebsd.org
Date: Mon, 25 Sep 1995 22:49:34 -0500 (CDT)
In-Reply-To: <199509251402.KAA12092@healer.com> from "Coranth Gryphon" at Sep 25, 95 10:02:39 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 536       
Sender: owner-hackers@freebsd.org
Precedence: bulk

> Agreed. I've said it before - symlink are only useful if you
> (for some reason) can't put something where it belongs, of if
> it really needs to be in two places at one: the latter translates
> as "cannot be easily gotten at in the proper place" or "a non-optimal
> location is hard-coded in something".

Symlinks have *lots* of uses other than that. I use them all the time.

For example, I'll install a program as "foocalc.version" and symlink
"foocalc" to it.

Symlinks are clean, self-documenting, and elegant, if used properly.