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

There's also "pear bundle" now: ssb@kirin(~/cvs/php/php5)$ pear bundle -d ext apd downloading apd-0.4p2.tar ... Starting to download apd-0.4p2.tar (-1 bytes) .........................................done: 189,440 bytes Package ready at '/home/ssb/cvs/php/php5/ext/apd' You can do this with any PECL release or tarball. All that would be needed is to run this command a couple of times from makedist. - Stig On Sun, 2003-11-30 at 18:59, Jani Taskinen wrote: > I kinda have thought all the time that those extensions > that will be in a release stay in the php-src CVS module. > And the rest is put into PECL, where people can find them > and use phpize or whatever to build them. > > Doesn't that 'pear install' thing work already? (sqlite, anyone?) > > --Jani > > On Sun, 30 Nov 2003, Wez Furlong wrote: > > >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. > >