> On Thu, Mar 29, 2001 at 11:50:29AM +0100, James Moore wrote:
> >
> > > abThu Mar 29 02:35:33 2001 EDT
> > >
> > > Modified files:
> > > /php4/ext/midgard config.m4 config.m4.session
> > > Log:
> > > - Typo fixed
> > > - config.m4.session updated to config.m4
> >
On Thu, Mar 29, 2001 at 11:50:29AM +0100, James Moore wrote:
>
> > ab Thu Mar 29 02:35:33 2001 EDT
> >
> > Modified files:
> > /php4/ext/midgard config.m4 config.m4.session
> > Log:
> > - Typo fixed
> > - config.m4.session updated to config.m4
>
> What does this fix do
> abThu Mar 29 02:35:33 2001 EDT
>
> Modified files:
> /php4/ext/midgard config.m4 config.m4.session
> Log:
> - Typo fixed
> - config.m4.session updated to config.m4
What does this fix do?? does it need to be included in 4.0.5?? or will ming
work without it??
James
--
missed the reply-all button...
> > At 00:29 20/3/2001, [EMAIL PROTECTED] wrote:
> > >Midgard is not exactly a layer above PHP, it's an extension to PHP,
> > >exactly like the session extension, or the gd extension.
> > >
> > >Here is my own point of view (far from objective, cause I'm from the
>
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 Pos
> "Thou shalt never break the CVS build" is one of the
> 'higher laws' around here :)
Amen to that one : )
-Jason
> Zeev
>
>
> --
> PHP CVS Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the l
Jani Taskinen wrote:
> >It probably won't get finished until people start using it. The midgard
> >people may be the right people for the job :)
>
> One question about this: Could we setup a separate module for Pear in the
> CVS? As now it's also 'bundled' with php.
That's exactly what I meant
Zeev Suraski wrote:
> >OK, substitute OCI8, the argument stands.
>
> That's only an interface module though. OCI8 isn't a part of PHP...
True, but as said: all elements that could possibly touch PHP
are LGPLd.
> >Not a problem for me. But how is PEAR being made available, then?
>
> PEAR is a
PEAR will be separate at some point, but let's not go overboard here. The
midgard stuff adds a total of 76K to the tar.gz file. Big deal.
-Rasmus
On Tue, 20 Mar 2001, Jani Taskinen wrote:
> On Tue, 20 Mar 2001, Zeev Suraski wrote:
>
> >> > Not a problem for me. But how is PEAR being made avai
On Tue, 20 Mar 2001, Zeev Suraski wrote:
>> > Not a problem for me. But how is PEAR being made available, then?
>>
>>We still don't have a good framework for having PEAR extensions that
>>contain PHP extensions written in C in them. That was always the goal, it
>>just hasn't been done yet. And
At 00:55 20/3/2001, Rasmus Lerdorf wrote:
> > > >MySQL access functions were in PHP long before it went open source. I'm
> > > >not saying that Midgard is on the same level of general usefullness
> > > >but just that the fact that there's an organization behind it
> > > >doesn't change it's licens
At 00:53 20/3/2001, Emiliano wrote:
>Zeev Suraski wrote:
>
> > >MySQL access functions were in PHP long before it went open source. I'm
> > >not saying that Midgard is on the same level of general usefullness
> > >but just that the fact that there's an organization behind it
> > >doesn't change it
At 00:29 20/3/2001, [EMAIL PROTECTED] wrote:
>Midgard is not exactly a layer above PHP, it's an extension to PHP,
>exactly like the session extension, or the gd extension.
>
>Here is my own point of view (far from objective, cause I'm from the
>Midgard team ;):
>Midgard is a CMS, like MySQL is a
Sterling Hughes wrote:
> Yes. But the midgard extension doesn't really do that, it provides some
> propreitary functions and classes for use by Midgard only. The reason its
> being distributed as an extension is --
Proprietary? If you mean 'only disclose functionality to deal with' then
all
ex
On Mon, 19 Mar 2001, Colin Viebrock wrote:
> > I don't think it belongs in PEAR at all. I could see the logic behind
> > distributing it with PHP, but don't see any reason to distribute it in
> > pear...
>
>
> Except that isn't this what PEAR was for all along? A collection of classes
> and a
> > >MySQL access functions were in PHP long before it went open source. I'm
> > >not saying that Midgard is on the same level of general usefullness
> > >but just that the fact that there's an organization behind it
> > >doesn't change it's licensing.
> >
> > MySQL was always opensource. It was
Zeev Suraski wrote:
> >MySQL access functions were in PHP long before it went open source. I'm
> >not saying that Midgard is on the same level of general usefullness
> >but just that the fact that there's an organization behind it
> >doesn't change it's licensing.
>
> MySQL was always opensource
At 00:30 20/3/2001, Emiliano wrote:
>Colin Viebrock wrote:
>
> > There is also the license issue (which I know has been discussed before).
> > But the first thing I read on the Midguard website is:
> >
> > Midgard will always implement an OS development to publishing
> > solution, future r
> > I don't think it belongs in PEAR at all. I could see the logic behind
> > distributing it with PHP, but don't see any reason to distribute it in
> > pear...
>
>
> Except that isn't this what PEAR was for all along? A collection of classes
> and add-on modules to extend PHP's functionalit
Colin Viebrock wrote:
> There is also the license issue (which I know has been discussed before).
> But the first thing I read on the Midguard website is:
>
> Midgard will always implement an OS development to publishing
> solution, future releases will include APIs for implementing
>
> I don't think it belongs in PEAR at all. I could see the logic behind
> distributing it with PHP, but don't see any reason to distribute it in
> pear...
Except that isn't this what PEAR was for all along? A collection of classes
and add-on modules to extend PHP's functionality?
I don't have
> I don't think it belongs in PEAR at all. I could see the logic behind
> distributing it with PHP, but don't see any reason to distribute it in
> pear...
Except that isn't this what PEAR was for all along? A collection of classes
and add-on modules to extend PHP's functionality?
I don't have
On Mon, 19 Mar 2001, Jani Taskinen wrote:
> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
>
> >On Mon, Mar 19, 2001 at 01:19:06PM -0600, Andrei Zmievski wrote:
> >> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> >> > This fix does not work because @MIDCONFIG_FILE@ in php_midgard.h does
> >> > n
On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> Andrei, problem is that build environment needs to be fixed, not module alone.
> This is really serious problem because it prevents people from using Midgard
> extension with, say, PHP 4.0.4pl1 (latest stable PHP4 version) though
> they could do it (
On Mon, Mar 19, 2001 at 01:19:06PM -0600, Andrei Zmievski wrote:
> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> > This fix does not work because @MIDCONFIG_FILE@ in php_midgard.h does
> > not substituted by PHP_OUTPUT using template file php_midgard.h.in.
> > Either fix building environment in
On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
>>fi
>>PHP_SUBST(MIDCONFIG_FILE)
>> - AC_SUBST(MIDCONFIG_FILE)
>> - AC_OUTPUT(php_midgard.h, [], [])
>> + PHP_OUTPUT(php_midgard.h, [], [])
>>AC_DEFINE(HAVE_MIDGARD, 1, [ ])
>>PHP_EXTENSION(midgard, $ext_shared)
>> fi
>This fix doe
On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
>On Mon, Mar 19, 2001 at 01:19:06PM -0600, Andrei Zmievski wrote:
>> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
>> > This fix does not work because @MIDCONFIG_FILE@ in php_midgard.h does
>> > not substituted by PHP_OUTPUT using template file php_mi
On Mon, Mar 19, 2001 at 08:28:20PM +0100, Jani Taskinen wrote:
> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
>
> >On Mon, Mar 19, 2001 at 01:19:06PM -0600, Andrei Zmievski wrote:
> >> On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> >> > This fix does not work because @MIDCONFIG_FILE@ in php_mid
On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> This fix does not work because @MIDCONFIG_FILE@ in php_midgard.h does
> not substituted by PHP_OUTPUT using template file php_midgard.h.in.
> Either fix building environment in PHP4 which does not allow output
> variable's value through template head
On Mon, Mar 19, 2001 at 06:38:09PM -, Jani Taskinen wrote:
> sniperMon Mar 19 10:38:09 2001 EDT
>
> Modified files:
> /php4/ext/midgard config.m4
> Log:
> Fix the build. Again.
> # Read README.CVS-RULES
> # And TEST before commit.
>
On Mon, 19 Mar 2001, Alexander Bokovoy wrote:
> abSun Mar 18 23:37:01 2001 EDT
>
> Modified files:
> /php4/ext/midgard config.m4 config.m4.session
> Log:
> Oops. Substitution code fixed
AC_OUTPUT is not intended to be called twice. Did not
PHP_OUTPUT work for you?
31 matches
Mail list logo
