[7892] in SIPB bug reports

home help back first fref pref prev next nref lref last post

Re: [Fwd: "ruby" interpreter symlink can be dangling]

daemon@ATHENA.MIT.EDU (Alex Coventry)
Tue Dec 18 18:59:53 2001

Date: Tue, 18 Dec 2001 18:59:44 -0500
Message-Id: <200112182359.SAA19731@QUICHE-LORRAINE.MIT.EDU>
From: Alex Coventry <alex_c@MIT.EDU>
To: jmorzins@MIT.EDU
CC: bug-sipb@MIT.EDU
In-reply-to: <3C1FD66B.1090503@mit.edu> (message from Jacob Morzinski on Tue,
	18 Dec 2001 18:51:07 -0500)


i guess it comes down to whether or not the benefit of hard-coding afs
paths in Alex' case outweighs the risk that a raft of changes'll be
required if the underlying filesystem ever changes again.  i used to
have hard-coded symlinks for python and my stuff in the outland locker,
but i switched to the current arrangement when i got some fud about it.
attachandrun scripts aren't such a big deal after you get used to them,
but they are definitely a barrier to entry for new users, so i would
like to go back to the old way.  on the other hand, it'd be nice to know
what the consensus on the issue is.

alex.

home help back first fref pref prev next nref lref last post