> At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote:
> > > >When we're past the prototyping phase and stuff stabilizes, a C
> > > >rewrite may be a good idea, but I don't think it is now.
> > >
> > > Well you know the most permanent things are temporary things such as
> > > prototypes.
> > > I also thought it would make much more sense to create something very small
> > > in C (maybe even Perl as it's installed on all systems) and use that.
> > > I'm not really sure anymore what this installer you are talking about looks
> > > like. So I think it would be good to get a small update and have a
> > > discussion of what we need on php-dev@.
> >
> >I see no issue with writing a prototype in PHP. The start of such a
> >prototype is in cvs (pear/script/pear)
> >
> >And yes, using XML is pretty much a no-brainer here. That will allow a
> >lot of different nifty tools to access the package information.
>
> For a start you don't have PHP installed on most systems. So PHP would need
> to compile itself and then fetch packages and recompile itself. Seems to me
> like the no-brainer isn't such a no-brainer.
We need to somehow work out the functionality. Once it is well-defined
other clients will come, I am sure. We can always provide a small
statically linked installer program which includes a stripped down PHP
binary and the appropriate Installer class.
If we were to write it in C we would most likely need to provide a
statically linked binary anyway for the different platforms as not
everyone will have access to a fully functioning development environment.
Despite the pervasiveness of Perl, chances are high that certain Perl
modules would be missing and then someone has to go looking for Perl
modules to install PHP packages.. Ouch!
-Rasmus
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
