From: Shane Z. <sh...@lo...> - 2008-02-26 14:22:07
|
On Feb 25, 2008, at 7:09 PM, Andre-John Mas wrote: > > On 25-Feb-08, at 18:25 , Shane Zatezalo wrote: > >> >> On Feb 22, 2008, at 3:18 PM, Andre-John Mas wrote: >> >>> Hi, >>> >>> With the constant reminder that IPv6 is on its way, I would be >>> interested to know if anyone has tried running Slashcode on an IPv6 >>> based Apache 2 and network? I don't imagine that there would be much >>> in the way of issues, but I would be curious to know whether any >>> turned up. >> >> >> Well seeing as Slash doesn't run under Apache 2 yet (see 'INSTALL' >> file for more info I think it's in there) I'd say no :( > > I didn't see anything about Apache 2 not being support in the > documents. > All I see are the minimum supported versions. Doing a search of the > internet shows compatibility issues, but the posts generally date 2004 > and before. > cooliod:current.untouched shane$ pwd /Users/shane/src/slash/current.untouched cooliod:current.untouched shane$ grep -ie 'Apache 2' * INSTALL: not compatible with Apache 2.x and we have no plans to port to 2.x :) > Is there a list of outstanding issues, with regards to Apache 2 and > Slashcode? That I don't know about. Maybe one of the OSTG guys will pipe in. I think there might have been an article on slashcode.com about it at one point or another. If memory serves, someone had started the modifications to make it work under Apache 2, or had got it working. I think at that time, modperl2 wasn't done yet. But if either happened, I don't recall ever seeing a patch submitted to Slash's sourceforge homepage with the needed changes. I could be wrong. I'd check the bugs-list, patch list and feature request list on the sf homepage. A subject change of Apache 2 and modperl 2 might be in order for the thread. That may get it more attention. I nearly ignored it because we, here, have no interest wrt IPv6. Hope that helps. Shane |