Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:2414 php.pear.dev:17565
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <022501c3362d$ec533490$0702a8c0@TITAN>
To: "Tomas V.V.Cox" <cox@idecnet.com>, <pear-dev@lists.php.net>
Cc: <internals@lists.php.net>
References: <395336819.20030619011936@idecnet.com>
Date: Thu, 19 Jun 2003 07:42:16 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Binary pecl packages
From: wez@thebrainroom.com ("Wez Furlong")

When I get a little more time (in about 2 months!) I will be completing the
work that I started on the .MSI installer generator for PHP.

This will generate an installer for the PHP distribution (including PEAR)
based on the .zip binary distros cooked by the snaps machine and meta data
from the source tree.

One of the things that should be possible is generating additional .MSI
files for PECL packages. From the example below, the 'peclfoo' package would
be generated as 'peclfoo-3.1.2-<STATE>.msi'.

Since .msi is "equivalent" to .rpm, we would then have the benefits of a
system supported package manager; the main thing that I can think of is that
it will handle upgrading extensions that are in use (if the user has enough
privileges) by being able to stop the web server while it updates the file,
or perhaps scheduling a restart if that is required.

--Wez.

> pecl package name
> -----------------
>
> The name of the extension would be:
>
> peclfoo-bin-<OS>-<ARCH>-3.1.2-<STATE>.tgz
>
> The os (Operating system) and arch (CPU type), would be the value
> returned by the OS_Guess class. STATE is a valid PEAR_Common package
> state.