Re: Re: cvs: pear-core /Archive Tar.php

Bonsoir Greg Beaver wrote:

Vincent Blavet wrote:

I'm not PEAR guru, so I think the problem should be managed by the PEAR Group. Yes, that is the authority, anyway, there's no problems only questions.

Glad to help solving them. Wellcome back Vincent

Here is the problem : Archive_Tar is used by the pear installer and is present in pear-core root filesystem and in the "regular" package system. The result is that most of the bugs are corrected in the regular package system, but somes are directly corrected in the pear-core by authorized people but not at the same time in the pear root filesytems. Which means I need to synch regularly the two. This situation is raised from time to time ...

The best thing to do is to remove package-Archive_Tar.xml and Archive/ from pear-core. I was not aware that Archive_Tar was also in pear/ until very recently, sorry about confusing commits on my part. Glad to have you in action Vincent :). The situation is the same with Getopt.

XML_RPC is in between.

I would like to put a README.PACKAGING file in pear-core/ that people can use to understand how to bundle up the various distroes of PEAR. Then, the only thing you need to do is any time you make a change to Tar.php, just sync it with php-src/pear branches PHP_4_4 and PHP_5_0. Then we'll be good to go. No, no synchs,

Core is pear and its immediate dependencies, if pear needs Archive_Tar, then Archive_Tar is in core. No synch ! If you don't like Archive_Tar being in core, don't use it. I consider it natural in core. a+ -- toggg