Re: Getting PHPTAL on PEAR2
| From: | Brett Bieber | Date: | Sat, 13 Feb 2010 14:04:03 +0000 |
| Subject: | Re: Getting PHPTAL on PEAR2 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53268@lists.php.net to get a copy of this message | ||
2010/1/27 Kornel Lesiński <kornel@aardvarkmedia.co.uk>:
> I've started porting PHPTAL to PEAR2-namespaced version and I've got some
> questions:
>
> 1. Is "pear2\HTML\Template\PHPTAL" namespace appropriate? I've noticed
> Savant's PEAR2 package uses pear2\Template (without "HTML" part) namespace.
Ah yes, well that's just where I put it. No contemplation was involved. :-)
> Which namespace prefix is correct?
I'd like to get the HTML\ part out of there, but that's just me.
> 2. What's the relationship between pear.php.net and pear2.php.net? Is the
> second one only temporary, or is it going to replace the first one? Is it OK
> to use pear.php.net for PEAR2-only package? If not, how can I get it on
> pear2.php.net?
We were looking at ways to integrate the two (meaning, bring the pear2
standards to pear1 packages), but it seems keeping them separate is
the direction we'll be heading.
The package release process isn't finalized yet... but, the entire
channel is in the pear2 repository. We need to figure out how releases
will work and get the process in place. I'm in favor of a
remote-release command being added to pear2 (with a documented
protocol so any channel could use it). That way pear devs can release
using the pyrus cli.
We could really use some help with pear2, if you're interested in
assisting, please let us know.
> FIY here's snapshot of work done so far:
>
> http://phptal.org/files/PHPTAL-1.2.2-namespaced.tar.gz
>
> It's not finished yet. package.xml hasn't been changed, and I know abstract
> classes and exceptions don't follow PEAR2 rules yet.
>
> --
> regards, Kornel
--
Brett Bieber