Actually putting midgard in PECL might be an approach - I think they basically want to move 'most' of the current extensions out of php/ext anyway
The only thing pending is a coherent packaging system. regards alan Emiliano wrote: >Vincent Stoessel wrote: > >>Another quick question: why does not midgard become an official extention >>of php? It does not seem like there is a huge barrier to entry, >>extension projects seem to come and go for php. >> > >Been there, done that, not likely to try again. They were complaining >about the size of the extension and anything else they could think of; >bottom-line: we were not welcome. When the scripting version of the >extension is done (Alexander, timeline on this?) it should be pretty >light-weight. I'm still not sure it's worth the hassle given our earlier >experience with the PHP developer crew, but at least we'll have better >papers. > >>one last question. Is there a way that the functionality of mod_midgard >>can be incorporated into mod_php4 ? That would save sysadmin and programmers >>from debugging 2 modules. >> > >Could: yes. Likely to ever happen? No. Possible to integrate in the >extension: no, since when the php4 extension is kicked into gear the >decision what file to serve has allready been made, so no midgard >requests. > >When mod_midgard switches over to scripting, that too will become >lighter and simpler. > >>./configure --with-midgard=/usr/local --enable_mdg_preparse \ >>--with-apxs=/usr/local/apache/bin/apxs --with-mysql=/usr/local >> > >Could be if we offer the scripting extension for inclusion. > >Emile > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
