Re: [RFC] Binary pecl packages
| From: | Jon Parise | Date: | Thu, 19 Jun 2003 02:27:44 +0000 |
| Subject: | Re: [RFC] Binary pecl packages | ||
| References: | 1 | Groups: | php.internals php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17564@lists.php.net to get a copy of this message | ||
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/)