Re: bash on debian
On Fri, 16 Feb 1996, David Engel wrote:
> > Tomorrow I will look into a strange thing about bash 1.14.6(1) here.
> > I ask you for a little check on your side on a debian system, to get a
> > better focus to the problem, that may be local to me. Could you please
> > repeat this:
> >
> > roro@ernie:tty4:~$ mkdir blurb
> > roro@ernie:tty4:~$ cd blurb
> > roro@ernie:tty4:~/blurb$ touch 0815
> > roro@ernie:tty4:~/blurb$ 0 [Now hit <tab> for completion.]
> >
> > I assume here, no executable matching 0* exists in your path.
> > On my system it segfaults (I would blame readline on the first shot).
>
> It segfaults for me too.
>
> > But don't worry about this, I will find it in any case. There are
> > only too much variables (libc, ncurses, readline) involved, which results
> > into low enthusiasm wrt beginning the hunt today.
>
> First things I would do to isolate the problem is rebuild bash without
> readline/ncurses and then with readline and termcap (the recently
> re-released old version) instead of ncurses.
I will summarize my observations so far:
1) GNU libreadline as standalone is apparently not active maintained.
2) There are packages which use readline and provide also the lib (bash,
gdb) and packages which use the installed (git, a hacked ftp, ncftp).
3) The bash maintainer, as the most important user, modified the readline.
4) A bash with standard libreadline fails (as of 1.14.6 at least)
5) libreadline depends on termcap or ncurses support
(maintainer in above paragraph means GNU maintainer)
What can we do:
1) Maintain the libreadline for the debian system by reimplement the bash
modifications.
2) Don't use the systems libreadline as a replacement (in bash, gdb)
3) Don't provide libreadline at all.
Comments?
Note: I talk here about bash-1.14.6-1.deb with:
root@ernie:tty1:~# ldd /bin/bash
libreadline.so.2.0 => /lib/libreadline.so.2.0
libncurses.so.3.0 => /lib/libncurses.so.3.0
libc.so.5 => /lib/libc.so.5.2.18
mfg
Rolf Rossius
Reply to: