Please note that this "fuck up" is in the debian version only, and
rxvt-256color is rather buggy to start with, and definitely not the
correct terminfo file for urxvt. The original urxvt uses "rxvt-unicode" and
"rxvt-unicode-256color" TERM values, respectively, which are the correct
values, and portable.

If debian wouldn't deliberately break its copy of rxvt-unicode these
problems wouldn't occur, and as added "benefit" debian wouldn't be
needlessly incompatible to the rest of the world (which uses the correct
terminfo files).

I don't know what the goal of all this breakage(*) is supposed to be,
but it would be preferable if debian clearly marked their version
of rxvt-unicode as completely incompatible to upstream and other
distributions (or alternatively maybe consider not continuously and
deliberately breaking it...)

If debian really insuist on doing their own incompatible patches, it
would be far better to rename the package to something like debian-rxvt,
and certainly set the TERM values to something like "debianurxvt" or so,
as opposed to introducing more subtle bugs and giving users a chance to
install the correct debian-specific terminfo on remote systems.

(*) debian has a long tradition of non-communication with upstream and
    deliberate bug-introducing patches, even going as far as removing our
    request to report bugs in the debian version to debian only from the
    FAQ section, as we are not responsible for their bugs.

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schm...@schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to