Re: Move old (or non-mainstream) extensions to PECL before beta 3

Perhaps I'm confused..... I had the impression that the point of moving obsolesced extensions to PECL was so that they WOULDN'T be included in the main source tarball. Then, should user X out there need ext/foo they can do a: pear install foo. If >that's< the case, then there need be no "pic up golden extensions at bundle time" script. The creation of a tarball is just what it already is. Are there any PECL extensions other than SQLite which are bundled at package time? What am I missing? -Sara ----- Original Message ----- From: "Wez Furlong" <wez@thebrainroom.com> Newsgroups: php.internals To: <internals@lists.php.net> Sent: Sunday, November 30, 2003 4:52 AM Subject: Re: [PHP-DEV] Move old (or non-mainstream) extensions to PECL before beta 3 > Hey, all I'm talking about is a script to put the golden extensions > into ext (and exclude the cruft) when we build our tarball distro. > > --Wez. > > > >> Why not go with RPM's then? The eays way is to split up the RPM's so > that we > > >> can have RPMs for the basic stuff like INI, Docs and all, then for the > > >> different sapis and then for all the extensions. See attached makerpm > for > > >> current state of work. > > > > > How do RPMs work on Gentoo, Debian, Windows, MacOSX...? > > > > It is impossible to find a solution that works for all systems. This RPM > > stuff at least is a way for all *nix systems. So the main problem is > > Windows again.