But that is beside the point. Nothing should block a release for an extended period of time which apr-dbd apparently is. There are technical reasons why apr and apr-util is built together into a single library on the NetWare platform. 99% of the time this is not a problem. But in this one case because of the refactoring of the LDAP code within apr-util, changes in apr-util affected the build files for apr on NetWare. NetWare is not blocking a release of anything. It's code is ready to go. It is the fact that apr-dbd API's are not fully cooked and ready to be released that is blocking things. There have been other changes within apr-util besides the NetWare build code that should be released as well. But they also can't be released because of apr-dbd. If apr-dbd is going to continue to hold up a release of apr-util for any reason, it needs to be pulled off into it's own -dev branch until it is ready.
Brad > >>>> On Tuesday, August 09, 2005 at 10:45 am, in message > <[EMAIL PROTECTED]>, Justin > Erenkrantz > <[EMAIL PROTECTED]> wrote: > >No, the problem is that Netware's build system is broken. It shouldn't be >tied together by version. Keeping them tied together breaks our compatibility >rules. We should always be able to mix and match apr and apr-util versions. > >Since Netware only has one maintainer, if it's not important for you to fix >it, then it's not important enough to block a release. -- justin
