Re: cvs: php4 /ext/midgard config.m4

Zeev Suraski wrote: > Not quite :) The main difference is that, unlike most other extensions, > this extension isn't a 'glue' layer that connects PHP to some external > resource. In this case, we're including the resource itself. It's more > similar to including the source code of MySQL or PostgreSQL inside PHP, not > a module that connects to them... There's quite a bit of Midgard that's not in PHP. But what you're saying is that there's too much application logic in our PHP code, I guess, and that's simply true. We're working on that right now. > - Is it mutually exclusive to other alternatives? The problem Colin raised > does exist, there are quite a few content management applications for PHP > out there, and it's a bit unfair to them to bundle a specific one inside PHP. Mutually exclusive? You mean if you activate the others won't work? No. > - The license issue - does the inclusion of midgard effect the overall > license restrictions of PHP or not? No. Period. We have no interest in doing something like it. Besides, talk about pointing a bazooka at your foot... > - Is the midgard group willing and interested in playing by the php-dev > rules? In particular, "Thou shalt never break the CVS build" is one of the > 'higher laws' around here :) Willing, absolutely. The initial checkin had a problem of always being activated, and the changes in PHP from 4.0.4pl1 to 4.0.5 appearantly changed some things in the autoconf setup and the generated files that caught us by surprise. Emile