On Thursday, June 19, 2003 4:27, Jon Parise wrote:
> 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'). Umm, yes, maybe it's better to just use "package". We have now native pear packages, rpm, msi is planned and others will surely come. Additionally we can generate the package description file and also call the tools for generating the whole package. Let's say something like: pear package [-t <type>] [-b] [-s] <package> -t <type> The type of package you want to generate (pear, rpm, msi, etc) -b Specifies a binary package -d Only generate the description package file You could even do a "pear package -t pear -d foo.tgz" to generate the package.xml file, at least the skeleton for hacking :) >> 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 personally met with some situations with non working RPMs, where I missed a lot this info. It's just a helper file, even suitable for better bug reporting. Umm, that takes me to the idea of a new "pear bugreport" command ;) > 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 Thanks, good info to look at. -- Tomas V.V.Cox mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
