Re: [Bashdb-devel] Re Autostuff patches.

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

Mikael Andersson writes:
 > 
 > Maybe we should remove the files build in debugger by the bash configure also ?
 > More specifically: debugger/dbg-pre.inc and debugger/doc/version.texi.

Yes, that would be a good thing to do. 

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

I accept this. The bash version change on the order of once every
couple of years. 2.05b hasn't changed all that often. In fact, it
hasn't so far :-).

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

Fine by me. By not changing things in (re)bash that aren't needed, we
limit the changes that will be needed when the next release comes out
and that would be a good thing.

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

Is rebash-2.05b-xxx and bash-2.05b-bashdb-xxx (or
rebash-2.05b-bashdb-xxx) clearer?

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

Another great idea. The top-level directory could include via "aclocal
-I debugger" Although debugger can't always assume rebash will be
there, rebash can probably assume that debugger will be around. 

If you can, I'd appreciate it if you make these great
suggestions. Many thanks.