Re: tcsh package
Hi,
i am the maintainer of csh.
> 1. To put tcsh binary in /bin (reason: there are people who use tcsh
> as roots and have remote /usr).
Don't do this. This has already been discussed a LONG while ago. The
consensus is that if people want tcsh in /bin they should copy it.
The ultimate rules are:
* root login shell is /bin/sh (or things may not work as expected)
* keep the root fs as small as possible.
If people want to work as root with tcsh, they should copy tcsh to /bin and
create a second root account (eg croot) with /bin/tcsh as login shell.
> 2. To make a symbolic link from /usr/bin to /bin/tcsh (reason:
> debian backward compatibility).
Unnecessary because tcsh has to stay in /usr/bin. (i moved /bin/csh to
/usr/bin/bcsh for the same reason)
> 3. To make a symbolic link from /usr/local/bin to /bin/tcsh (reason:
> compatibility with other Unices).
Totally wrong! A package MUST NOT touch /usr/local! This is local stuff
and none of your business (that too has already been discussed)
> The package is almost ready by now. It's the same version of tcsh
> (6.06) but with some minor configuration changes... And, of course,
> new dpkg standards :)
Please check the open bug reports first before releasing the package,
especially that regarding the coexistence of csh and tcsh.
Right now csh conflicts with tcsh because csh was changed to fix that bug
and tcsh is not yet fixed.
If you have additional questions about coexistence of csh/tcs, then contact
me outside the lists...
Dominik Kubla
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The text above represents my personal opinion and does not represent the
official position of my employer on the issue(s) discussed.
Any official statement made on behalf of my employer by me is marked as such.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: