Masatake YAMATO writes:
> I write what I know. In Autotools book written by Gary V. Vaughan, et
> al., bootstrap.sh and autogen.sh are introduced for this purpose. The
> difference between bootstrap.sh and autogen.sh is runnint configure at
> the end of script or not; autogen.sh runs and bootstrap.sh does not.
> I cound find autogen.sh in many projects. However, bootstrap.sh is
> good for cross compiling.
Thanks for the information! I guess then the best thing to do is to
make it so cvscompile.sh, bootstrap.sh and autogen.sh all work.
By the way I've set up a mailing list
bas...@li.... (I'm copying that list to see if
it *really* works.)
If in the past there has been private mail, it's not been by intention
but just a lack of getting an open discussion list set up. Your mail
has been very helpful to this project and perhaps others will find the
information you write useful too.
> > The idea of putting this in an open CVS was to encourage multiple
> > developers. (Personally, I'm not a big fan of bash. However I am too
> > often forced to use it.) If you would like write access work on
> > development and make changes to this project let me know.
>
> I cannot do much things, however, I could do some small things.
> Please, add me. My sourceforge account name is "masata-y".
> First my task is putting a bashdb.el screenshot to the project
> web page:)
Great. Yet Again, thanks!
> The buggiest question is: does the bash author know this project?
You mean the current bash maintainer, not the original other. I think
so. But it is hard to know what the maintainer knows and doesn't since
he seems often to be uncommunicative often. Two years ago, I submitted
some patches and received no word on it - whether it was received,
needed changes or whatnot. Before starting this I sent info on what
the changes were to get to the first version of this. Again nothing.
|
