Re: Re: cvs: php4 /pear Makefile.in /pear/Archive Tar.php
| From: | Vincent Blavet | Date: | Wed, 23 Jan 2002 09:38:01 +0000 |
| Subject: | Re: Re: cvs: php4 /pear Makefile.in /pear/Archive Tar.php | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-4109@lists.php.net to get a copy of this message | ||
----- Original Message -----
From: "Stig S. Bakken" <ssb@alltheweb.com>
To: <cox@idecnet.com>
Cc: "Jon Parise" <jon@php.net>; "Vincent Blavet"
<vincent@blavet.net>;
<pear-dev@lists.php.net>
Sent: Wednesday, January 23, 2002 9:04 AM
Subject: Re: [PEAR-DEV] Re: [PEAR-CVS] cvs: php4 /pear Makefile.in
/pear/Archive Tar.php
> 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?
It's OK for me. I prefer to have Archive_Tar in the standard package
mechanism.
I will manually synchronize the CVS tree (only the Tar.php file) in order to
have an updated version in php4/pear. This seems to be usefull for people
who download Core PEAR from there. I'm not sure there is a possible auto
mechanism.
I start to look at the installation stuff, but more on the package install
tools than on the PEAR release with PHP. So don't know exactly how works the
<scriptfile lang="sh"> tag. I will have to look.
On the PEAR manual part, I release Archive_Tar as a Package under the File
System Category and not the Core PEAR.
Vincent
>
> - Stig
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: pear-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>