Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:2408 php.pear.dev:17564
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 18 Jun 2003 22:27:44 -0400
To: pear-dev@lists.php.net, internals@lists.php.net
Message-ID: <20030619022743.GA17288@csh.rit.edu>
Mail-Followup-To: pear-dev@lists.php.net, internals@lists.php.net
References: <395336819.20030619011936@idecnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <395336819.20030619011936@idecnet.com>
User-Agent: Mutt/1.5.3i
Subject: Re: [PEAR-DEV] [RFC] Binary pecl packages
From: jon@php.net (Jon Parise)

On Thu, Jun 19, 2003 at 01:19:36AM +0200, Tomas V.V.Cox wrote:

> package creation
> ----------------
> 
> pear build -b peclfoo-3.1.2.tgz
> 
> The -b (or --bin) option generates the package containing only the
> compiled extension and the files marked with role "php", "doc", "test",
> "data" or "script" with the original package.xml modified
> automagically (explained in the next point).

I think 'pear dist' would be a more appropriate name for this
operation (or maybe just an extension of 'pear package').
 
> An idea would be to create a COMPILED_AT.txt file with some data about
> the env where the extension was compiled at, like the
> php version, the php_uname(), the extra libs versions, os vendor
> version, /etc/shadow file, etc.

I'd suggest BUILDINFO.txt.  I'm not sure if this is entirely
necessary, but I can see where it would be useful.

I'll also point you to distutils[1].  The Python folks spent a lot of
time thinking about these kinds of problems, and the result is a quite
good system.

[1] http://www.python.org/doc/current/lib/module-distutils.html
 
-- 
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)