Re: Re: PEAR and Smarty
| From: | Stig S. Bakken | Date: | Sat, 20 Jul 2002 10:46:47 +0000 |
| Subject: | Re: Re: PEAR and Smarty | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7801@lists.php.net to get a copy of this message | ||
On Wed, 17 Jul 2002, Martin Jansen wrote:
> On Wed Jul 17, 2002 at 06:5211PM +0200, Bertrand Mansion wrote:
> > <mail@martin-jansen.de> wrote :
> > > One fine day Andrei Zmievski (who is now know to be prisoned by Stig
> > > Bakken in Boston) pointed out that he wouldn't object if someone came
> > > up with a plan to merge Smarty into PEAR. But since noone did so at
> > > that time and since Smarty has it's own prominent homepage
> > > (http://smarty.php.net/) now, I don't see a reason why it should be
> > > merged into PEAR.
> >
> > Well, that's not what I remind happened. I remember that Andrei didn't want
> > to conform to pear coding standards (helloWorld not hello_world). I wonder
> > how he does now that he is Stig's prisoner. :-)
>
> That was another point in the discussion. IIRC we got down to the
> point where Andrei a) did not want to change the API and b)
> nevertheless welcomed everyone who wanted to merge Smarty into PEAR
> (while keeping the API).
>
> >Other than that, I must admit I don't
> > really care about where Smarty is hosted.
>
> That's where I see a big opportunity for PEAR in the future: Well
> known existing applications like Smarty, Phorum or sth. similar can
> make full usage of the PEAR installer by simply providing package
> definitions and/or .tgz-files containing their releases.
>
> They don't need to conform to the coding standards of PEAR or need to
> change their hosting situation, but they can use our infrastructure
> for easy publishing.
I agree.
> >If one can use the pear installer
> > to install it, then it will be just fine. But the Smarty configuration file
> > has to remain editable (and then, not located in /usr/lib/php). This is the
> > only problem I see.
>
> It should be posssible (in the future) to install webapps that put
> files into a pre-defined directory in the virtual host tree (like
> /var/www/www.mydomain.com/var/), which is editable by the user via
> FTP, telnet or SSH. Actually I'm not sure how far Stig went with this,
> but he can surely clue us in.
Haven't gotten around to it yet, but the idea is to let users choose
between a virtual host setup ala www.appname.example.com or a subdirectory
setup ala www.example.com/appname/.
- Stig