Re: Re: cvs: php4 /pear Makefile.in /pear/Archive Tar.php
| From: | Stig S. Bakken | Date: | Wed, 23 Jan 2002 08:04:46 +0000 |
| Subject: | Re: Re: cvs: php4 /pear Makefile.in /pear/Archive Tar.php | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4106@lists.php.net to get a copy of this message | ||
cox@idecnet.com wrote:
>
> > On Mon, Jan 21, 2002 at 10:18:14PM +0100, Vincent Blavet wrote:
> >
> > > Archive/Tar is now present on CVS in php4/pear/ and pear/.
> > > How should I manage any improvment, bug correction, and so on ? On both
> > > locations ?
> >
> > Being that Archive/Tar is required by php4/pear/, I suppose that
> > would be the best place to maintain it.
> >
>
> Tar.php is actually a big part of the PEAR packages manager stuff. I guess it
> will be even more delayed if Vincent didn't come with that great class :) I'm
> also of the idea it should be in php4/pear. Now this class is taken from pear/
> and included in the brach of each new PHP release. This is not bad at all but
> having it in the main branch could make things easier for people who downloads
> PEAR from CVS (more people than one can guess).
>
> But IMHO it should be in pear/ as a package, have it own release cycle in the
> web, it documentation and I also vote to have the Stig's
> php4/pear/scripts/phptar script as part of this package.
Makes sense. So the file list needs to define scripts to install then.
The challenge is doing it in a portable way. Maybe if "pearize" did
autoconf-equivalent substitutions and the package format got a tag like
<scriptfile lang="sh">, it could be done.
Apart from that, I'm in favor of just syncing pear/Archive_Tar to
php4/pear, to make things easier. I don't think it's a good idea to
move it there, because it will be more difficult to upgrade it later.
How does this sound to you Vincent?
- Stig