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]
