Shibboleth Developers

[Ian Young <>]

Scott Cantor wrote:

> So, my quandary is whether I can afford the time right now to actually make
> contact and attempt to get the real log4cpp fixed so that it actually works,
> and I just don't like the odds. My preferred direction is to fork it. I can
> do that as long as I keep all the original copyright intact, and any of the
> changed code is LGPL'd by Internet2.

For what it's worth, looking at the state of that project on
sourceforge, I don't fancy your odds either.  Even if you got the
patches (which have been sitting in the patch queue since 2005) applied
to the main code, you'd need to persuade them to make their first formal
release since umpteen oatcake in order to solve the Debian problem.

That's not to say that it might not be worth pushing in that direction
anyway, as otherwise you're responsible for the fork forever.  But I
wouldn't make any plans that depended on resolving the problem any time
soon, say for Shib 2 time.

> The main purpose of the fork is to stamp the thing 1.0 and rename it, so
> that it won't interfere with the "real" log4cpp anymore. In doing this, I
> will probably need to make some changes to allow for either my version or
> some potential future version of log4cpp that actually works to be used.

Yes.  Because eventually you want this package to be someone else's
problem again.

        -- Ian's 2c