hi Mathieu, On Fri, Jun 07, 2013 at 10:08:51AM +0200, Mathieu Parent wrote: > Package: pkg-php-tools > Version: 1.6 > > As discussed on the ML [1], Composer "Dependency Manager for PHP " [2] > seems to get some audience, pkg-php-tools can be improved to support > its format. > > Two different solutions: > - use Composer API [3] (this requires packaging it) > - parse the composer.json file directly
i can try packaging it, although i haven't done much PHP packaging work at all before except for initial work on wp-cli. as far as i can see, composer itself is a self-contained phar file, which can be downloaded directly (http://getcomposer.org/composer.phar for the latest snapshot, or a specific version listed on http://getcomposer.org/download/) or via a PHP script which checks local PHP setup and a few other settings before retrieving the phar via curl and saving it locally. in terms of Debian packaging (at least as a starting point), would it be ok to simply package the upstream phar file or would it be necessary for debian/rules to actually include the full source tree (git://github.com/composer/composer.git), run phpunit tests, build the phar file from scratch, etc? any pointers to best practices or examples would be very helpful. (i am looking at pkg-php packages in anonscm.debian.org but i'm not sure which packages there would be closest in terms of layout to a possible composer Debian package... perhaps pkg-php/debpear.git?) [...] thanks andrea -- andrea rota Xelera - IT infrastructures http://xelera.eu/contact-us/
signature.asc
Description: Digital signature
