Date: Tue, 26 Sep 1995 01:06:46 -0400 From: Coranth Gryphon <gryphon@healer.com> To: hackers@freebsd.org, peter@taronga.com Subject: Re: ports startup scripts Message-ID: <199509260506.BAA15489@healer.com>
next in thread | raw e-mail | index | archive | help
>From owner-freebsd-hackers@freefall.freebsd.org Tue Sep 26 00:47:55 1995
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
From: peter@taronga.com (Peter da Silva)
> it really needs to be in two places at one: the latter translates
> as (1) "cannot be easily gotten at in the proper place" or (2) "a
> non-optimal location is hard-coded in something".
> For example, I'll install a program as "foocalc.version" and symlink
> "foocalc" to it.
"foocalc.version" is not easy to rememeber, "foocalc" is.
Hence my category 1 case.
> Symlinks have *lots* of uses other than that. I use them all the time.
> Symlinks are clean, self-documenting, and elegant, if used properly.
Agreed. I just don't think it is a good idea to design a mechanism around
depending upon then. Because that means you are designing it to need
the file in two places at once.
-coranth
------------------------------------------+------------------------+
Coranth Gryphon <gryphon@healer.com> | "Faith Manages." |
| - Satai Delenn |
Phone: 603-598-3440 Fax: 603-598-3430 +------------------------+
USMail: 3 Hansom Drive, Merrimack, NH 03054
Disclaimer: All these words are yours, except Europa...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509260506.BAA15489>