At 23:51 06/12/2005, Pierre wrote:
On Tue, 06 Dec 2005 10:53:37 -0800
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Pierre wrote:
> > On Tue, 06 Dec 2005 09:03:16 +0100
> > [EMAIL PROTECTED] (Derick Rethans) wrote:
> >
> >>> * Introduce xmlwriter extension via a symlink from pecl into core
> >>> a
On Tue, 06 Dec 2005 10:53:37 -0800
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Pierre wrote:
> > On Tue, 06 Dec 2005 09:03:16 +0100
> > [EMAIL PROTECTED] (Derick Rethans) wrote:
> >
> >>> * Introduce xmlwriter extension via a symlink from pecl into core
> >>> and as other XML extension enable it
Pierre wrote:
On Tue, 06 Dec 2005 09:03:16 +0100
[EMAIL PROTECTED] (Derick Rethans) wrote:
* Introduce xmlwriter extension via a symlink from pecl into core
and as other XML extension enable it by default.
Make sure that the licences gets switched back to the PHP license
then...
It is alread
Hi,
Would it be a problem to dual-license the extension? So
users/distributors can choose if they want to use it under the PHP
License or under BSD/LGPL/whatever.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Pierre wrote:
On Tue, 06 Dec 2005 09:03:16 +0100
[EMAIL PROTECTED] (Derick Rethans) wrote:
* Introduce xmlwriter extension via a symlink from pecl into core
and as other XML extension enable it by default.
Make sure that the licences gets switched back to the PHP license
then...
It is alr
On Tue, 06 Dec 2005 09:03:16 +0100
[EMAIL PROTECTED] (Derick Rethans) wrote:
> > * Introduce xmlwriter extension via a symlink from pecl into core
> > and as other XML extension enable it by default.
>
> Make sure that the licences gets switched back to the PHP license
> then...
It is already do
> * Introduce xmlwriter extension via a symlink from pecl into core and as
> other XML extension enable it by default.
Make sure that the licences gets switched back to the PHP license then...
Derick
This message was sent usin
Hello Pierre,
Thursday, December 1, 2005, 8:58:45 PM, you wrote:
> On Thu, 1 Dec 2005 20:52:32 +0100
> [EMAIL PROTECTED] (Marcus Boerger) wrote:
>> Hello Ilia,
>>
>> i prefer only allowing PHP License in 'stock PHP'.
> The question was not what "we" prefer but what is allowed or not, and
> w
As per the notes at http://www.php.net/~derick/meeting-notes.html,
section 2.4.2: 'We make "var" an alias for "public" and remove the
warning for it.'
Could something like the attached patch be included as part of 5.1.2?
Michel Sisolak
[EMAIL PROTECTED]
___
On Thu, 1 Dec 2005 20:52:32 +0100
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Hello Ilia,
>
> i prefer only allowing PHP License in 'stock PHP'.
The question was not what "we" prefer but what is allowed or not, and
why.
To be a little more precised, I see no reason to not allow BSD-like or
ot
Hello Ilia,
i prefer only allowing PHP License in 'stock PHP'.
marcus
Thursday, December 1, 2005, 5:01:07 PM, you wrote:
> Rasmus Lerdorf wrote:
>> One of the reasons is that this would be the first extension we bundle
>> which isn't under the PHP license.
> Not a question about xmlwriter sp
Rasmus Lerdorf wrote:
> One of the reasons is that this would be the first extension we bundle
> which isn't under the PHP license.
Not a question about xmlwriter specifically, but licensing policy in
general. Does your comment imply that only and only extension released
under the PHP license are
On Thu, 01 Dec 2005 14:30:07 +0530
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Jani Taskinen wrote:
> > On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
> >
> >> * Enable xmlreader extension by default, as we do for all XML
> >> extensions.
> >
> > Done. Also made it use the right configure opt
Marcus Boerger wrote:
Sure, but until that happens I don't think it should be included.
Same here. The discussion was on IRC and between Rob & Pierre and i thought
they changed back but didn't do so yet.
The license is changing. It was actually supposed to have changed
yesterday. Pierre
Hello Rasmus,
Thursday, December 1, 2005, 10:08:41 AM, you wrote:
> Jani Taskinen wrote:
>> Isn't that solved by just simply changing the license by the author?
> Sure, but until that happens I don't think it should be included.
Same here. The discussion was on IRC and between Rob & Pierre
Jani Taskinen wrote:
Isn't that solved by just simply changing the license by the author?
Sure, but until that happens I don't think it should be included.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 1 Dec 2005, Rasmus Lerdorf wrote:
Jani Taskinen wrote:
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from
You forgot one thing: pecl/filter !
It definately should be included, with the EXPERIMENTAL flag of course.
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Jani Taskinen wrote:
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from pecl into core and as
other XML extension e
On Wed, 30 Nov 2005, Ilia Alshanetsky wrote:
* Enable xmlreader extension by default, as we do for all XML
extensions.
Done. Also made it use the right configure option.
* Introduce xmlwriter extension via a symlink from pecl into core and as
other XML extension enable it by default.
On Wed, 30 Nov 2005, Andi Gutmans wrote:
Is our confidence level on xmlwriter high? Just asking as I'm not sure how
It's very high. I need it too. :)
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Andi Gutmans wrote:
> Sounds like a good plan to me.
> Is our confidence level on xmlwriter high?
I'd say, so.
> Just asking as I'm not sure
> how broadly it's been used and if we expect the API to have limitations
> or require changing at some point.
My understanding is that the API is pretty
Sounds like a good plan to me.
Is our confidence level on xmlwriter high? Just asking as I'm not
sure how broadly it's been used and if we expect the API to have
limitations or require changing at some point.
Thx Ilia!
At 08:10 PM 11/30/2005, Ilia Alshanetsky wrote:
Here is a brief outline o
23 matches
Mail list logo