On Fri, 30 Mar 2001, James Moore wrote:
> > Ummmmm...
> >
> > If I'm not mistaken, the midgaurd extension itself, only provides
> > functionality to the "midguard" application? Ie, end-users of midguard
> > will not use the functions and classes exported by the extension, only
> > midguard will use that functionality?
> >
> > If so, I'm not too sure it would be a good idea to include the midguard
> > extension in PEAR either...
>
> There is nothing stopping someone else making a php app that uses midguard
> extension if they want to.
Right, but from what I understand the functions only make sense for the
midguard application.
> I can see your point but if there is a feeling that it should be
> distributed with PHP in someway PEAR seems the most logical place. By your
> arugment why should midguard be in ext/ either as noone but people running
> midgard use it. PEAR is somewhere where it would be easy to retive from
> (eventually) and is hopefully where we will eventually have other non
> standard extensions.
>
Yes, and no offense intended, I don't see why the midguard people don't
just distribute the extension *with* midguard. I could see some sense in
distributing it with PHP, because then users of midguard really didn't
have to worry about compiling twice, etc, its already built-in to
php. While I'm not for that idea (it adds 70k of bloat), I don't see the
point in distributing it with PEAR. When you distribute it with pear
there is no advantage for the midguard people (or anyone) that I can see
(or advantage greater than just distributing the midguard extension with
midguard itself).
-Sterling
--
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]
