I don't know why, but I always get two copies of replies. Murray Cumming wrote: > > On Wed, 2001-10-17 at 22:51, D. Stimits wrote: > > Murray Cumming wrote: > > > > > ...snip... > > > > > > > > > > > > What is required to get the ball rolling on this as a change? Should I > > > > submit an altered package that is similar to the sane_includes? > > > > > > sane_includes fixes all of the problems. I will push for those changes > > > to be applied *after* the next bugfix release. We've already been > > > through the process with that. > > > > Don't forget to propagate the make install prefix bug fix to > > sane_includes, it looks like it was formed before the prefix changes. > > Of course. > > > > > > > > This is > > > > holding back a project due to wanting to see whether it gets fixed on > > > > both win32 and linux (the cvs change already fixed the broken make > > > > install on linux/UNIX) for the package layout. I suspect that maybe it > > > > is fear of the dramatic changes to the cvs tree, more than anything, > > > > that is delaying a more sane official package layout. > > > > > > I believe that we decided that that's worthwhile and possible. There's > > > no point in discussing it until after the next release. > > > > What kind of time frame is expected for the next bugfix release? It also > > sounds like the bugfix release itself will not reflect sane_includes, is > > that correct? > > Haven't I just been saying that? If I'm waiting until after the release > to make the changes, then it's likely that the release will not include > the changes. > > If the bugfix release does not reflect sane_includes, is > > there a probable time frame beyond the bugfix release that will reflect > > sane_includes? > > Nobody can predict the future.
Is there an approximation of what a typical time is between releases for bugfixes? Is it typical for it to occur monthly? D. Stimits, [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
