On 15 Nov 2005 09:26:35 -0600, email@example.com <firstname.lastname@example.org> wrote:
> Garrett Rooney <email@example.com> writes:
> > I believe it has not yet been officially released. Considering the
> > number of changes that have gone in to 1.3.x post rc2, I would suspect
> > a rc3 release sometime soon, so mid-to-late december seems pretty
> > likely to me.
> It's not the number of changes, it's their nature. If the changes to
> 1.3.x since RC2 are not for severe bugs, then they could wait until
> 1.3.1, and there would be no need for RC3. But if they are for severe
> bugs, then an RC3 would be needed.
> * r17297 [merge of r17257]
> Emit a workaround for bugs in SWIG 1.3.25 and earlier which cause
> SWIG_GetModule to be called with the wrong number of arguments.
r17257 is necessary in order for our SWIG bindings to compile with GCC
2.9x, so I consider it to be an important fix. For this fix alone, I
believe it is worth rolling RC3.
r17279, which removes recursive symbolic links from our build tree, is
also an important fix. r17279 prevents Python from recursively
importing modules, such that "libsvn.core" imports
"libsvn.libsvn.core", and "libsvn.libsvn.core" imports
"libsvn.libsvn.libsvn.core", and so on. Besides this, recursive
symbolic links also break "scp", thus making it difficult for
developers to copy the Subversion build tree from one machine to
another. I think it would be a very good idea to include this fix in
David James -- http://www.cs.toronto.edu/~james
Received on Tue Nov 15 18:13:32 2005