headers
Daniel O'Connor | 1 Sep 2010 01:55
Picon
Gravatar

Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Wed, Sep 1, 2010 at 3:24 AM, till <till <at> php.net> wrote:

> [ Taking this discussion to pear-dev. ]
>
> Hey Daniel et all,
>
> I think I'm the only person using svn:externals in a package, maybe
> you can ignore them on checkout to quickfix this?
>
> I'm also wondering why I included it to start with - I don't remember
> why it's there. I'll check into this in a bit.
>
>
I believe a unit test fails if it's not there :S
Permalink | Reply | 1 comment |
headers
Daniel O'Connor | 1 Sep 2010 02:11
Picon
Gravatar

Re: BC breaks: Cache_Lite, PHP_Documentor

>
> I'm a bit reluctant to leave as is for too long (read: years) - both
>> packages are fairly popular, and if PHP 5.4/6 kills off the methods; the
>> migration path for a heck of a lot of other users is much more painful
>> (Cache_Lite ->  Zend_Cache, PHPDocumentor ->  ... doxygen?).
>>
>
> You are missing my point again: the migration path for users is to stop
> relying on magic_quotes_runtime and switch it off.

The migration path for packages is to quit calling
> set_magic_quotes_runtime() unconditionally (I now see that phpDocumentor
> does that): this will prevent errors for people who are not relying on
> deprecated functionality.
>
> Agree, but... how do we get the magic quotes people to fix their
environments without raising errors (and thus introducing a BC break)? I'm
talking the ancient, PHP4, there's no E_DEPRECATED raised folks as opposed
to the PHP 5.* folks. All one of them.

At what point do we go "oh nuts to those PHP4 users on
http://stopphp5.org/, they keep posting about python anyway,  let's
make a minor BC break to
make it visible"?

The don't-leave-it-years desire - yes, we could conditionally check things;
but I imagine in the next major version; get_magic_quotes functionality
would probably go the way of the dodo too - so we end up having to do this
dance again for the PHP 5.* users.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel O'Connor | 1 Sep 2010 03:49
Picon
Gravatar

Re: [PEAR-QA] A 'graveyard' for packages / unloved packages

>
> A quick note, moving packages to another channel is currently not supported
> in PEAR, in terms of, people are not auto migrated over. This would cause
> problems for people.
>
> - Helgi
>
> Apart from that hurdle, what do people think of
http://graveyard.pear.php.net/ ?

You'll have to add in a hosts file entry (38.108.46.133
graveyard.pear.php.net) ; because I have NFI how to do DNS entries.

The process for 'graveyarding' a package is a bit involved at the moment:

   1. Grab code - svn co http://svn.php.net/repository/pear/graveyard
   2. Grab the deprecated code, and if needed edit the package.xml until
   it's valid package 2.0
   $ pear convert package.xml
   3. Roll a new release with appropriate change log notes
   $ pfm
   4. Edit the channel to be graveyard.pear.php.net
   5. $ pear package
   6. $ pear svntag package.xml
   7. Regenerate the channel with pirum
    $ php pirum add Foo_Bar-1.2.3.tar.gz
   8. Commit the lot
   svn commit -m "Held funeral for Foo_Bar - proud father of Foo_Bar2"
   9. Pull an svn update on sg1
   sudo svn up /var/www/html/graveyard
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel O'Connor | 1 Sep 2010 04:14
Picon
Gravatar

Re: [PEAR-QA] A 'graveyard' for packages / unloved packages

Also:
http://www.flickr.com/photos/clockwerx/4946614295/

as a mockup
Permalink | Reply | 0 comments |
headers
Alexey Borzov | 1 Sep 2010 10:07
Picon
Favicon

Re: BC breaks: Cache_Lite, PHP_Documentor

Hi Daniel,

On 01.09.2010 4:11, Daniel O'Connor wrote:
>>
>> I'm a bit reluctant to leave as is for too long (read: years) - both
>>> packages are fairly popular, and if PHP 5.4/6 kills off the methods; the
>>> migration path for a heck of a lot of other users is much more painful
>>> (Cache_Lite ->   Zend_Cache, PHPDocumentor ->   ... doxygen?).
>>>
>>
>> You are missing my point again: the migration path for users is to stop
>> relying on magic_quotes_runtime and switch it off.
>
> The migration path for packages is to quit calling
>> set_magic_quotes_runtime() unconditionally (I now see that phpDocumentor
>> does that): this will prevent errors for people who are not relying on
>> deprecated functionality.
>>
>> Agree, but... how do we get the magic quotes people to fix their
> environments without raising errors (and thus introducing a BC break)? I'm
> talking the ancient, PHP4, there's no E_DEPRECATED raised folks as opposed
> to the PHP 5.* folks. All one of them.
>
> At what point do we go "oh nuts to those PHP4 users on
> http://stopphp5.org/, they keep posting about python anyway,  let's
> make a minor BC break to
> make it visible"?
>
>
> The don't-leave-it-years desire - yes, we could conditionally check things;
(Continue reading)

Permalink | Reply | 0 comments |
headers
till | 1 Sep 2010 15:23
Picon

Re: Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Wed, Sep 1, 2010 at 1:55 AM, Daniel O'Connor
<daniel.oconnor <at> gmail.com> wrote:
> On Wed, Sep 1, 2010 at 3:24 AM, till <till <at> php.net> wrote:
>
>> [ Taking this discussion to pear-dev. ]
>>
>> Hey Daniel et all,
>>
>> I think I'm the only person using svn:externals in a package, maybe
>> you can ignore them on checkout to quickfix this?
>>
>> I'm also wondering why I included it to start with - I don't remember
>> why it's there. I'll check into this in a bit.
>>
>>
> I believe a unit test fails if it's not there :S
>

I guess the "problem" is that you test "trunk" and not the release. So
whenever someone works on stuff, this will break your shiny test
suite. ;-)
Personally, I also break trunk when I implement stuff, I'd be more in
favor of testing releases.

Till

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 0 comments |
headers
till | 3 Sep 2010 15:14
Picon

Re: Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Wed, Sep 1, 2010 at 3:23 PM, till <till <at> php.net> wrote:
> On Wed, Sep 1, 2010 at 1:55 AM, Daniel O'Connor
> <daniel.oconnor <at> gmail.com> wrote:
>> On Wed, Sep 1, 2010 at 3:24 AM, till <till <at> php.net> wrote:
>>
>>> [ Taking this discussion to pear-dev. ]
>>>
>>> Hey Daniel et all,
>>>
>>> I think I'm the only person using svn:externals in a package, maybe
>>> you can ignore them on checkout to quickfix this?
>>>
>>> I'm also wondering why I included it to start with - I don't remember
>>> why it's there. I'll check into this in a bit.
>>>
>>>
>> I believe a unit test fails if it's not there :S
>>
>
> I guess the "problem" is that you test "trunk" and not the release. So
> whenever someone works on stuff, this will break your shiny test
> suite. ;-)
> Personally, I also break trunk when I implement stuff, I'd be more in
> favor of testing releases.
>
> Till
>

Always enjoy being heckled for something and then I'm talking to myself! :D
(Continue reading)

Permalink | Reply | 5 comments |
headers
Brett Bieber | 3 Sep 2010 15:45
Picon
Gravatar

Re: Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Fri, Sep 3, 2010 at 8:14 AM, till <till <at> php.net> wrote:
> I'd love to see "vendor" in the standards to have one way to do it
> across the board.

vendor or lib is fine by me.

Speaking of which, a vendor dir containing a pyrus controlled registry
of PEAR packages is very easy to do —
https://docs.google.com/document/edit?id=1TbN7rhmcnHLknlV2r8B1mG0bIp6knajLB8iMbnmgN-U&hl=en#

-- 
Brett Bieber

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 4 comments |
headers
till | 3 Sep 2010 15:47
Picon

Re: Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Fri, Sep 3, 2010 at 3:45 PM, Brett Bieber <brett.bieber <at> gmail.com> wrote:
> On Fri, Sep 3, 2010 at 8:14 AM, till <till <at> php.net> wrote:
>> I'd love to see "vendor" in the standards to have one way to do it
>> across the board.
>
> vendor or lib is fine by me.
>
> Speaking of which, a vendor dir containing a pyrus controlled registry
> of PEAR packages is very easy to do —
> https://docs.google.com/document/edit?id=1TbN7rhmcnHLknlV2r8B1mG0bIp6knajLB8iMbnmgN-U&hl=en#
>

That's pretty sweet. A future blog post?

Till

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 3 comments |
headers
Brett Bieber | 3 Sep 2010 16:16
Picon
Gravatar

Re: Re: [PEAR-BUG] Bug #17835 [WFx]: WARNING: Function 'spliti' is deprecated, please use 'preg_split'

On Fri, Sep 3, 2010 at 8:47 AM, till <till <at> php.net> wrote:
> On Fri, Sep 3, 2010 at 3:45 PM, Brett Bieber <brett.bieber <at> gmail.com> wrote:
>> On Fri, Sep 3, 2010 at 8:14 AM, till <till <at> php.net> wrote:
>>> I'd love to see "vendor" in the standards to have one way to do it
>>> across the board.
>>
>> vendor or lib is fine by me.
>>
>> Speaking of which, a vendor dir containing a pyrus controlled registry
>> of PEAR packages is very easy to do —
>> https://docs.google.com/document/edit?id=1TbN7rhmcnHLknlV2r8B1mG0bIp6knajLB8iMbnmgN-U&hl=en#
>>
>
> That's pretty sweet. A future blog post?

Yeah that's the plan. I was waiting for the next pyrus release — but
here we are, two months later and the next version still isn't out.

-- 
Brett Bieber

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 2 comments |

Gmane