[pkg-php-pear] tests in composer packages

Thomas Goirand zigo at debian.org
Sat Jun 29 17:05:37 UTC 2013

On 06/29/2013 01:50 AM, andrea rota wrote:
> however, running phpunit in the build folder just shows a
> message asking to install (via composer) the dependencies of the code
> being tested/packaged: this could either be achieved via a system-wide
> composer install (on which i'm working), but i'm not sure whether
> phpunit should rely on system-wide library installs (i.e. packaged in
> Debian) or if it would be best to let the system-wide composer binary
> work as a per-project installer, creating a 'vendor' folder in the build
> directory, downloading the required dependencies and installing them in
> 'vendor', creating the autoloader code - again, in 'vendor' - and
> running tests there.

You should use the system-wide installed library, and Build-Depends: on
that. That's how all other packages are doing.

You can leave the unit tests aside for the moment though, and add the
feature later on, if you feel it is more easy to do this way.


P.S: Don't need to CC: me, I'm reading the list. Andrea, do you wish to
be CC-ed?


More information about the pkg-php-pear mailing list