Re: [PHP-DEV] Midgard
Emiliano wrote: Midgard extension contains 200k of vanity images. This is unreasonable bloat to the core of PHP. Can you please remove them? They've been removed days ago. My mistake, they were removed from our own CVS. We forgot to do that at cvs.php.net. The mistake has been rectified. Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
Peter "[DiSAStA]" Petermann wrote: Well right now it won't really solve it because pear is included in the distribution. However, the idea behind pear is to be something more similar what if midgard would be handled like php-gtk? How would that be? Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
Andi Gutmans wrote: OK, my mistake. So moving php4/ext/midgard to php4/pear/midgard would solve this? Well right now it won't really solve it because pear is included in the distribution. However, the idea behind pear is to be something more similar to CPAN which means both PHP and C code. OK, but CPAN is huge too. Does the build process differ here? And like my previous question, are there examples on how to build config.m4s, and other supportive files, so an extension can easily be built as an php-dloabable, a static extension, and a static extension in a statically-compiled PHP (into Apache itself)? The easiest way to get it working is "cd php4; cp -r /path/to/midgard ext; ./buildconf". That's all people need to do in order to get it to work with their vanilla PHP. You can check out some of the other extensions to see how to build a shared library but with my example it's not necessary. What I couldn't find there is how to detect that we're being built using apxs or statically in apache, for example. There is also the phpize stuff (which I don't know). It's something like phpize /path/to/midgard and then compiling the midgard as a shared library. I think the first example I gave you is probably good enough though. The phpize methods works (it's what we use right now), but loading the midgard extension for every request does not have my preference. Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
There is also the phpize stuff (which I don't know). It's something like phpize /path/to/midgard and then compiling the midgard as a shared library. I think the first example I gave you is probably good enough though. The phpize methods works (it's what we use right now), but loading the midgard extension for every request does not have my preference. So put: extension=midgard.so in your php.ini file. Then it is loaded by default at startup. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
Stanislav Malyshev wrote: E With the PHP4 version of Midgard, patching is no longer a E necessity. It's an ordinary extension like the others. Ah, so parser modifications are out? Good to know. Yes, they are. Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
At 22:11 12/2/2001, Rasmus Lerdorf wrote: The idea here is that Midgard has a large installed base of users, all of whom have to run a modified version of PHP. The extension, albeit rather large at this point, is supposed to provide the basic functionality in the standard PHP distribution so people will not have to run a modified PHP to use midgard. The intent here is not to have all of Midgard in PHP. Hopefully the Midgard folks will work towards making the extension as small as possible. With the PHP4 version of Midgard, patching is no longer a necessity. It's an ordinary extension like the others. Perhaps it would be an idea to move it out of the main PHP CVS (into another cvs module) for now and put links on php.net, personally I would really like to see things like this in PEAR which is where I feel they should be. Is there any work being done on some sort of deamon/server for PEAR so people get a client build when PHP builds and then they can just tell it to fetch various modules for PHP from php.net and any mirrors etc. In the end somthing like $pearclient get midgard which would do everything needed (IE fetch midgard from PHP.net place in it right place etc) would be cool then all the client would have to do is either build it as .so or rebuild php with --enable-midgard for example. Just my ?0.02 James -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
James Moore wrote: With the PHP4 version of Midgard, patching is no longer a necessity. It's an ordinary extension like the others. Perhaps it would be an idea to move it out of the main PHP CVS (into another cvs module) for now and put links on php.net, personally I would really like to see things like this in PEAR which is where I feel they should be. But PEAR is a repository for scripts written in PHP, right? php4/ext/midgard is a 'regular' (albeit admittedly large) PHP extension, written in C. Is there any work being done on some sort of deamon/server for PEAR so people get a client build when PHP builds and then they can just tell it to fetch various modules for PHP from php.net and any mirrors etc. In the end somthing like $pearclient get midgard which would do everything needed (IE fetch midgard from PHP.net place in it right place etc) would be cool then all the client would have to do is either build it as .so or rebuild php with --enable-midgard for example. That would indeed be nice. Well, since we're on the topic of re-seperating, are there examples on how to build config.m4s, and other supportive files, so an extension can easily be built as an php-dloabable, a static extension, and a static extension in a statically-compiled PHP (into Apache itself)? Emile -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
Emiliano wrote: But PEAR is a repository for scripts written in PHP, right? PHP Extension and Add-On Repository. Extensions and Add-Ons, written in either PHP or C, are welcome :-) -- sebastian bergmann e-mail : [EMAIL PROTECTED] homepage : http://www.sebastian-bergmann.de make a gift : http://wishlist.sebastian-bergmann.de measure the usability of your web application - http://phpOpenTracker.de -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
RE: [PHP-DEV] Midgard (Was: cvs: php4 /ext/midgard .cvsignore...)
With the PHP4 version of Midgard, patching is no longer a necessity. It's an ordinary extension like the others. Perhaps it would be an idea to move it out of the main PHP CVS (into another cvs module) for now and put links on php.net, personally I would really like to see things like this in PEAR which is where I feel they should be. But PEAR is a repository for scripts written in PHP, right? php4/ext/midgard is a 'regular' (albeit admittedly large) PHP extension, written in C. I might be wrong here but PEAR at the moment only has PHP scripts in it but I thought that it was also aimed to have PHP C extensions in it and if this is not the case then why?? Would it not be possible to do this then some of less used extensions can go in there (printers, iisfuncs etc) I personally this this would be a good place for them then those looking for them can find them rather than them sitting in CVS and not being included in distributions as they are still experimental. James -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] midgard, was RE: [PHP-DEV] Legal solution: RE: [PHP-DEV]Non-GPL readline
On Wed, 17 Jan 2001, Sam Liddicott wrote: Midgard, soon to use php4 is to be released GPL (according to their website www.midgard-project.org). How will this work; will it just be the patch to php4 that makes it INTO migard that will be GPL, or midgard+PHP that will be GPL. The owner of GPLed code can grant third parties the right to use the code with certain non-GPLed programs (i.e. PHP). The merged result will inherit all license conditions from both code bases (unless the owner of the code expressively states something else). The result won't be solely under the GPL, but under a (cumbersome and sometimes contradictionary) set of conditions. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] midgard, was RE: [PHP-DEV] Legal solution: RE: [PHP-DEV] Non-GPL readline
At 12:08 17/1/2001, Rasmus Lerdorf wrote: They obviously can't distribute PHP under the GPL. And I wish they would just contribute whatever patches to PHP they think need so Midgard could use a vanilla PHP install. Stas talked to them a while ago, some of their patches don't really align with PHP's syntax / design. It's not a matter of licensing. How bad could it be? Anything we can't just toss into a --with-midgard switch? -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] midgard, was RE: [PHP-DEV] Legal solution: RE: [PHP-DEV] Non-GPL readline
At 12:02 17/1/2001, Sam Liddicott wrote: If (b) is true then surely we need officialy a choice of license (or at least project-midgard.org does) As Rasmus said, obviously they can't distribute PHP under the GPL - and there's nothing wrong with that. It doesn't mean that they can't distribute PHP (plain), and midgard under their own license. Zeev -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] midgard, was RE: [PHP-DEV] Legal solution: RE: [PHP-DEV] Non-GPL readline
At 12:17 17/1/2001, Rasmus Lerdorf wrote: At 12:08 17/1/2001, Rasmus Lerdorf wrote: They obviously can't distribute PHP under the GPL. And I wish they would just contribute whatever patches to PHP they think need so Midgard could use a vanilla PHP install. Stas talked to them a while ago, some of their patches don't really align with PHP's syntax / design. It's not a matter of licensing. How bad could it be? Anything we can't just toss into a --with-midgard switch? Language-syntax level stuff (parserscanner)... Zeev -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]