Re: [Bashdb-devel] make debugger thoughts

[Masatake Y. <je...@gy...>]

> Given this split in goals, I think it best to maintain this initially
> as a seperate track. Although this track is alpha, I think it has some
> important and useful changes and needs early exposure to best grow
> this the right way. I don't think it should be tied down to the GNU
> make 3.81 release schedule and similarly I don't think the 3.81
> release schedule should be tied down to having this be flawless.
> 
> Two possibilities I see for this then are in GNU make's CVS as a
> separate branch, or completely outside such as for example bashdb's
> CVS (in sourceforge.net). The latter is the most convenient for me
> since that's an area I already have write access to and can easily
> make releases from. I've used that in the past for example to extend
> ddd to support the new bash debugging I wrote. 

I think you should talk to GNU Make developers.
Development style of GNU Make seems that more open than Bash.
So it is worth to contact them.
(http://savannah.gnu.org/mail/?group=make)

As a user, I'm happy if your code are merged to GNU Make official
tar.gz. If merging is the goal, general it is better to work near to 
official source tree:) Of course, in some case diplomacy is needed.

> As Masatake YAMATO has pointed out, down the line I'll need to set up
> GNU arch (http://www.gnuarch.org/) or something like that in order to
> track changes across the two branches.

I feel gnuarch is too strong weapon. It gives you real freedom about
development. You can reflect the GNU Make's CVS repository to your
gnuarch's archive by
cscvs(http://wiki.gnuarch.org/moin.cgi/Additional_20Tools).  My idea
is use gnuarch as your ace if the diplomacy is failed.

Masatake