Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 19 Jun 2003 13:11:51 +0200
Reply-To: "Tomas V.V.Cox" <cox@idecnet.com>
Message-ID: <207967392.20030619131151@idecnet.com>
To: "Wez Furlong" <wez@thebrainroom.com>
CC: pear-dev@lists.php.net, internals@lists.php.net
In-Reply-To: <022501c3362d$ec533490$0702a8c0@TITAN>
References: <395336819.20030619011936@idecnet.com>
 <022501c3362d$ec533490$0702a8c0@TITAN>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PEAR-DEV] Re: [PHP-DEV] [RFC] Binary pecl packages
From: cox@idecnet.com ("Tomas V.V.Cox")



On Thursday, June 19, 2003 8:42, Wez Furlong wrote:

> 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.

Could this .msi generator be integrated into the pear cmd? A "pear
makemsi" command would be cool.

-- 
 Tomas V.V.Cox                          mailto:cox@idecnet.com