Re: [Bashdb-devel] Re Autostuff patches.

[R. B. <ro...@pa...>]

I hvave made some small additions to the recent good autostuff work.

A little background. The debugger directory I view as an independent
unit. Right now it needs the bash program from the parent directory
but hopefully it might not in the future. So I've been trying to keep
things under debugger self-contained.

When I did a "make distcheck" in the debugger directory, the tarball
crated was bash-2.05b.tar.gz. This would be the name for an unmodified
bash rather than the debugger portion of an enhanced bash. I've
changed the distribution tarball to bash-2.05b-bashdb-xxx.tar.gz. I
realize this is a little confusing given the parent directory tarball
which includes this is bash-2.05b-debugger-xxx.tar.gz. Perhaps that
tarball name should change to rebash-2.05b-xxx-tar.gz.

Another problem in the debugger directory was the fact that if
autoconf chose to run again it couldn't find acinclude.m4 since that's
only in the top-level directory, not the debugger directory. What I've
done here is have the top-level configure.in copy this file to
debugger; acinclude.m4 is also added to the bashdb tarball:
bash-2.05b-bashdb-xxx.tar.gz. I considered adding it to bootstrap.sh,
but then changes in the top-level acinclude.m4 wouldn't get reflected
below. Another possibility would be to set the ac macro directory with
-I to include the top-level directoyr. But again this makes the debugger
less independent.

Finally, I've removed debugger/dbg-main.inc from CVS (although it's
still in the Attic for CVS) since this is now derived from
dbg-main.inc.in.

As always if you have improvments, problems with this, comments, or
suggestions, let me know.