I am the the upstream author of Bashish and intend to provide packages in sync with the following Bashish releases.

Packages will be avaliable from http://bashish.sourceforge.net/debian

add the following to your sources.list:
deb http://bashish.sourceforge.net/debian ./

debian/control:
--------------------
Source: bashish
Section: shells
Priority: optional
Maintainer: Thomas Eriksson <[EMAIL PROTECTED] >
Build-Depends-Indep: debhelper (>> 4.0.0 )
Standards-Version: 3.6.2

Package: bashish
Architecture: all
Depends: dialog
Suggests: xfonts-artwiz, bash (>=3.1) | zsh (>=4.2.6) | c-shell | fish (>= 1.11) | rc (>= 1.7)
Description: Theme environment for text terminals
 Bashish is a theme enviroment for text terminals. It can
 change colors, font, transparency, and background image
 on a per-application basis. Additionally Bashish supports
 prompt changing on common shells such as bash, zsh, and
 tcsh.
 .
 The target audience for Bashish, are users who:
  * Want a good looking prompt.
  * Want to customize the appearance of terminal commands.
  * Want informative titles based on the command arguments.
  * Need different fonts for different applications - eg.
    Chinese, Japanese, OEM Terminal fonts.
 .
 Compared to writing your own aliases for commands, Bashish
 supports very complex customization options and does not
 affect neither aliases/functions nor redirected commands.
 .
 web site: http://bashish.sourceforge.net


--- end debian/control ------

Following are my reasons for some lintian overrides:

csh-considered-harmful
----------------------------------
Bashish includes quite a few lines of c-shell scripting (even more
than lintian[1] detects[2]) which is discouraged[3] by the
Debian policy.

The c-shell code in Bashish provides a prompt enviroment for csh and
tcsh - just as it provides prompts for bash, zsh, rc, fish and lsh.

So, removing the c-shell code would give quite a loss in functionality
for those who prefer to use the c-shell interactively without giving
benefits for code maintainance in Bashish.
For example, without the c-shell code, Bashish would not be able
to automatically load on c-shell, neither would themes be allowed
to contain prompts for c-shell.

As the author of Bashish I thus have decided not to remove[4] the
c-shell specific code from Bashish.

[1] lintian, a Debian policy checker
[2] location of c-shell code:
/usr/share/bashish/main/prompt/csh/*
/usr/share/bashish/bt/default/prompt.csh
/usr/share/bashish/bt/default/prompt.tcsh
/usr/share/bashish/bt/override/prompt.csh
/usr/share/bashish/bt/override/prompt.tcsh
and c-shell prompts contained in various themes.
[3] http://www.debian.org/doc/debian-policy/ch-files.html#s-scripts
[4] this is a decision based upon providing functionality, not
    a technical one.

cheers

/Thomas Eriksson

Reply via email to