Bug 26196 - csh and tcsh overwrite each other's files!
Bug#: 26196 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: grobian@gentoo.org Reported By: hans.w.wurst@gmx.de
Component: Unspecified
URL: 
Summary: csh and tcsh overwrite each other's files!
Keywords:  
Status Whiteboard: 
Opened: 2003-08-08 05:05 0000
Description:   Opened: 2003-08-08 05:05 0000 
csh and tcsh ebuilds both install the following files:

/bin/csh
/etc/csh.cshrc
/etc/csh.login

csh also installs:

/etc/csh.logout (read by tcsh as well)

proposal:

1. new ebuild (csh-startup-scripts):
- csh and tcsh depend on it
- contains (actually usable) startup scripts compatible 
  with both shells
- startup scripts are removed from csh and tcsh ebuilds

2. new ebuild (tcsh-csh)
- depends on tcsh
- only installs the csh->tcsh symlink
- said symlink removed from tcsh ebuild
- csh and tcsh-csh block each other

(why do I get the feeling all shell ebuilds except bash 
are not really intended to be used?)

------- Comment #1 From Tavis Ormandy (RETIRED) 2003-08-08 07:02:52 0000 ------- 
I'll block tcsh in csh. I think its quite cheeky of tcsh to put that symlink in
there without checking :)

------- Comment #2 From Tavis Ormandy (RETIRED) 2003-08-08 07:04:13 0000 ------- 
actually, i'll wait for comments from tcsh maintainers.

------- Comment #3 From Reporter 2003-08-08 17:02:11 0000 ------- 
Thanks for the quick response, a fix would be really helpful here
as with the current ebuilds neither csh nor tcsh are really useful
without a complete rewrite of both /etc/cshrc and /etc/cshrc.login.

The way they are now, csh installs those files mostly empty (except
for sourcing /etc/csh.env) and tcsh attempts to be newbie-friendly 
(.tcsh-config) at the same time as annoying more advanced users
(and doing some other weird stuff I don't want to repeat here).

The more I think of it, it may be a good idea to make these two 
files part of baselayout to keep them in sync with what bash does.

------- Comment #4 From Reporter 2003-10-23 20:54:10 0000 ------- 
still experiencing the /bin/csh conflict

------- Comment #5 From Jeffrey Gardner 2005-03-09 09:31:49 0000 ------- 
It appears that for me, ncbi-tools depends on both csh and tcsh, but when I
emerge -u world I get a blocker.

Calculating world dependencies ...done!
[blocks B     ] app-shells/tcsh (is blocking app-shells/csh-1.29-r3)



# qpkg -q csh
app-shells/csh-1.29-r3 *
DEPENDED ON BY:
app-shells/tcsh-6.12-r3 *
DEPENDED ON BY:
        ncbi-tools-20041020-r1


# qpkg -q tcsh
app-shells/tcsh-6.12-r3 *
DEPENDED ON BY:
        ncbi-tools-20041020-r1
app-shells/tcsh-6.12-r3
DEPENDED ON BY:
        sci-biology/ncbi-tools-20041020-r1


Food for Thought,
je_fro

------- Comment #6 From Jakub Moc (RETIRED) 2005-10-25 14:46:59 0000 ------- 
Re-assign a mis-assigned bug.

------- Comment #7 From Fabian Groffen 2005-10-26 01:45:01 0000 ------- 
@csh maintainer:
I only look at tcsh-6.14-r1, because that ebuild solves lots of problems users
have (had) and is about to be stabled.
- I think I should remove making the csh -> tcsh symlink from tcsh ebuild.
- for the csh.* and perhaps profile.d/*.csh files we should perhaps indeed
create a meta package, as they are bound to cause collision-protect problems
- I think csh should not block tcsh (after above has been solved)

------- Comment #8 From Fabian Groffen 2005-11-02 14:17:28 0000 ------- 
tcsh now only adds csh -> tcsh symlink if csh doesn't exist yet.

------- Comment #9 From Fabian Groffen 2005-11-02 23:19:33 0000 ------- 
new version of csh ebuild (csh-1.29-r4.ebuild) removes offending (empty) files
and the block on tcsh.

------- Comment #10 From Fabian Groffen 2005-11-25 05:14:07 0000 ------- 
The newest versions of csh and tcsh do not block each other any more, or
overwrite their files, hence I consider this bug fixed.