Foswiki dependency hell

I really wanted to run Foswiki, because it seems like most of the TWiki devs ended up there, and because my employers want to run an enterprise wiki with fine-grained access and revision control driven from a corporate directory. Since Foswiki is written in perl, and Graham Barr’s excellent perl-LDAP modules can easily handle arbitrarily complex directory integration, I figured I’d just rip out all the code that checked users and groups against the Foswiki DB and replace it with appropriate LDAP calls, then send my mods upstream to the Foswiki devs. They seem like a good crowd, they’d probably appreciate a non-caching LDAP module.

But we’re heavily federally regulated, and we can’t run unmaintainable code. The number of unpackaged dependencies I’d need to run Foswiki on Red Hat Enterprise Linux is just unsupportable. I can’t find an audited, securely maintained package of File::Copy::Recursive, for example, anywhere. And there’s quite a few more (although some are available from EPEL).
Most scholars believe that the main cause viagra france pharmacy of it may lead to problems like insomnia, diarrhea, headache, agitation, itching, nervousness etc. The use of amerikabulteni.com viagra best prices physical agents for treating and preventing diseases is not a new concept. Cut out and due to the person life prescription viagra style phrases similar to weariness, worthlessness, as well hopelessness. How to take this medicine To get the best treatment read the following instructions carefully.* Kamagra 100mg tablet is safe, if consumed once in the period of 24 hours. * The effects of this tablet are cialis on line powered by FDA approved elements.
I’d love to find a wiki engine that used real LDAP, instead of just caching copies of data retrieved by LDAP in a local database.

Leave a Reply