given how painful (for the developers) the 10.1->10.2 upgrade was, I
think they'd probably just as soon let the users be responsible for the
their own environment settings.
On Wed, 2003-02-26 at 15:33, Remi Mommsen wrote:
> Hi,
>
> Yes indeed this could be a problem. However, I have a customized
Hi,
Yes indeed this could be a problem. However, I have a customized
csh.cshrc since 10.2 came out and none of the incremental updates since
then touched those files. If this would happen (maybe when moving to
10.3) one would have to rerun the script which adds the 'source
/sw/bin/init.csh'. I
Indeed, one could do that. I've even suggested to people who want to
set fink up for all users on a machine. The problem (which I had
forgotten about) is that incremental operating system updates (10.2.x ->
10.2.x+1) could wipe it out.
Since the Users Guide gets updated more frequently, it might
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, Feb 26, 2003, at 14:32 US/Eastern, Remi Mommsen wrote:
Another solution to this problem would be to add the 'source
/sw/bin/init.(c)sh' not to the users local files, but to the system
wides /etc/bashrc resp. /etc/csh.cshrc. The /etc/csh
Hi,
Another solution to this problem would be to add the 'source
/sw/bin/init.(c)sh' not to the users local files, but to the system
wides /etc/bashrc resp. /etc/csh.cshrc. The /etc/csh.cshrc is read
before the local .cshrc or .tcshrc of csh and tcsh. This could even be
done automatically duri
There has been additional discussion about .tcshrc interfering with
.cshrc . A suggestion was made about adding to the documentation the
info about what to do in the event of a .tcshrc . That seems like a lot
of work to me.
--
Alexander K. Hansen
Associate Research Scientist, Columbia University
