Hi,
ok, missed that. But i hope you know this would only really
work on Windows I guess. Even sharing binaries from one Linux
distribution to another is not possible sometimes because of
the different GLIBCs used. IMHO that cries for more work then
there would be benefit for.
System administration is task of the user. It always was and
will always be.
- Markus
On Thu, May 30, 2002 at 12:12:15PM +0300, Marko Karppinen wrote :
> Markus:
> > Honestly I see this being a point beyond the task of PECL.
> > There are too many things which can get fucked up (I just see
> > a secenery where someone accidantly installs libxml2 through
> > PECL though he has it in the system but in a non-standard
> > path). Really, this does not belong to PECL by all means.
>
> I think I didn't make myself clear enough. I didn't mean that
> PECL should install system libraries; it could instead download
> php-specific copies of them (like ext/gd/libgd) and use them
> for building the extension binary *only*.
>
> This is what I meant when I said that it would be just as hard
> as actually bundling the libraries.
>
> There has already been talk about including binary versions of
> the extensions in PECL. Presumably they would also contain the
> dependencies. My proposal is to make the *complete* source to
> them available for building on the client side, too.
>
> And, just for the record, I also oppose the idea of bundling
> something as huge as libxml2 into the main distribution.
>
> mk
>
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
--
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
Wishlist: http://guru.josefine.at/~mfischer/wishlist
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
