Re: [Bashdb-devel] Re Autostuff patches.

[Mikael A. <sn...@te...>]

On Tuesday 26 August 2003 05.29, R. Bernstein wrote:
> 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.
>

My we should remove the files build in debugger by the bash configure also ?
More specifically: debugger/dbg-pre.inc and debugger/doc/version.texi.
I understand that those are there to use the version in bash for the version 
in debugger. But if we accept updating version number in both directories we 
can move building those files into debugger also. We could also remove most 
of the debugger specific configure things from the bash directory if we note 
in the README/INSTALL that running ./configure --help=recursive is a good 
idea if you want to know the options available.

> 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.

The naming conventions are a bit confusing and if anything can be done to make 
clearer what the different packages is, so much better. 

> 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.
>

Why not have acinclude.m4 only in debugger and copy it to the
top-level dir ? In this way debugger is almost completely self-contained with 
the above mentioned fixes regarding files built by top-level but used by the 
debugger build.

> 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.
>

Naturally

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

/Mikael