Shibboleth Developers

["Scott Cantor" <>]

> My interpretation of the following statement is that there would be a
> new dist of shib 1.3 with the new log4cpp - yes?

The new dist of 1.3 isn't strictly because of that, there are many, many
reasons I'm planning that.

> If so, why?  Why not just freeze 1.3?

2.0 will take time to stablize, I have many, many sites in production here
using it that will require long term maintenance of the branch, and for
various build-related reasons, I need a single library set for both branches
and 1.3's lib set is very out of date. There are also numerous fixes needed,
64-bit support, etc.

The logging thing is really incidental to all that.

> The rest of what you describe seems reasonable
> to me.  A shame that log4cpp has been abandoned.

It's not strictly abandoned, I just don't trust the minimal life support
it's on. If thread safety is viewed as some kind of "optional" bonus that
wouldn't have been fixed years ago, I don't care to hitch my horse to that
wagon.

-- Scott