Thanks for the information on bash 3.0. I've ftp'd
bash-3.0-alpha.tar.gz and made a preliminary scan. I'm absolutely
delighted that the timestamped history is there (I found that very
helpful when a friend's server was hacked into in determining who did
what.)
I'm in the middle of another project right now, but I hope next week
to compile the bash 3.0 alpha and test with the current debugger CVS
sources that live outside of the bash execuable.
Some small things that come to mind:
- a recent change was made to be able to customize where the debugger
gets installed. The prevailing opinion seems to be that default
location should be $prefix/share rather than $prefix/lib.
- In CVS, the debugger is installed in "debugger" so it would be
helpful to have the directory called that.
- I've been improving the regression-testing scripts to use
information from configure so that spurious messages (e.g. this test
may fail if job control or arrays are not around) are removed and to
make them more easily runnable as a standalone routine.
Again, thanks.
Chet Ramey writes:
> own...@po... wrote:
>
> > Date: Sat, 27 Sep 2003 15:40:19 +0900 (JST)
> > From: Masatake YAMATO <je...@gy...>
> > Subject: bashdb
> > In-reply-to: <030...@ni...>
> > To: bas...@cw...
> > Cc: ro...@pa...
> [...]
> >
> >>The first alpha release of bash-3.0 is now available with the URL
> >>
> >>ftp://ftp.cwru.edu/hidden/bash-3.0-alpha.tar.gz
> >>
> >>This tar file does not include the formatted documentation (you
> >>should be able to generate it yourself).
> >
> >
> > I've just gotten bash-3.0-alpha.tar.gz.
> > I have some questions.
> >
> > Is new bashdb suported in this version?
> >
> > configure.in:
> > if test -z "${DEBUGGER_START_FILE}"; then
> > DEBUGGER_START_FILE=${ac_default_prefix}/lib/bashdb/bashdb-main.inc
> > fi
> > I cannot find ${srcdir}/lib/bashdb in the tar ball. Only a little explanation
> > about debugger in the documents.
> >
> > It means only C code of debugger is included in bash-3.0?
>
> In my alpha version, it is. I am assuming that Rocky will perform the
> necessary work to integrate his code into bash-3.0, since the changes
> I made are not identical to the ones he submitted, and by the time
> bash-3.0 hits the street the two will be in sync.
>
> Rocky, feel free to either replace examples/bashdb or add a bashdb
> subdirectory directly in the source directory.
>
> Chet
|
