Re: PECL != Siberia
| From: | Stig S. Bakken | Date: | Fri, 14 Jun 2002 23:41:33 +0000 |
| Subject: | Re: PECL != Siberia | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-85225@lists.php.net to get a copy of this message | ||
Okay, one problem seems to be solved: go-pear supports Windows now.
Download http://pear.php.net/go-pear and do "php -q
go-pear".
Next issue is prebuilt extensions. I really want to have package
signatures (with pgp/gpg) before going there, but again I'm not sure
what the most feasible approach would be on Windows.
Anyway, here's what I have in mind:
Today packages have a layout like this:
package.xml
pkg-version/file1
pkg-version/file2
pkg-version/file3
...
During "pear package", the package.xml file is re-created including md5
checksums of all the files. By just adding a package.sig file during
packaging that contains package.xml's signature, the entire package is
in practice signed.
By default, the pear installer should only install prebuilt extensions
signed by a trusted key (we have to bootstrap this trust network somehow
too). As an option, you may add trusted keys or disable the signing
requirement for prebuild extensions and pre/post install/uninstall
scripts.
Some advice on how to verify pgp signatures on Windows would be
appreciated though. :-)
- Stig
On Mon, 2002-06-10 at 22:05, Shane Caraveo wrote:
> It's a tough one :)
> Well, being able to build like on unix shouldn't be too hard to do, just
> have to call nmake on the dsp, but that wont work for the vast majority
> of users. Someone needs to provide prebuilt extensions that can be
> downloaded via pear, and unfortunately, I don't see any way other than
> having a build per version of PHP. So the built extensions would have
> to have a filename like: extname-phpversion-extversion.zip. Another
> idea would be to have the extensions built for windows on the server
> side, and cached if one was already built.
>
> Shane
>
> Stig S. Bakken wrote:
> > You tell me :) We currently have no nice way of bootstrapping PEAR on
> > Windows like we have on Unix (with "make install-pear-installer" and
> > go-pear). What would be the most sensible way of giving Windows users
> > something ala go-pear?
> >
> > - Stig
> >
> > On Sun, 2002-06-09 at 18:49, Shane Caraveo wrote:
> >
> >>Hmm, what is happening for win32?
> >>
> >>Stig S. Bakken wrote:
> >> > With the latest PEAR installer (version 0.90), PECL extensions are now
> >> > built and installed during "pear install/upgrade" on Unix systems.
> >> >
> >> > First: upgrade PEAR to 0.9 with "pear upgrade PEAR".
> >> >
> >> > If you have the xmms libraries and php_gtk installed, you can see it in
> >> > action by doing simply "pear install xmms". The output is like this:
> >> >
> >>
> >>
> >>
> >
> >
> >
>
>
--
Stig Sæther Bakken, Fast Search & Transfer ASA, Trondheim, Norway
http://pear.php.net/wishlist.php/ssb