[pkg-php-pear] Bug#692353: ITP: php-wpcli -- PHP PEAR module for a WordPress CLI interface

Thomas Goirand zigo at debian.org
Mon Nov 5 19:24:17 UTC 2012

On 11/06/2012 12:28 AM, andrea rota wrote:
> thanks - i have prepared an initial package which works ok on a couple
> of production nodes: what would be the best way to make the code
> available for review?

Upload the package somewhere (it doesn't have to be mentors.debian.net,
as long as download is fast enough), and give the link to the .dsc file
(that file is the result of a dpkg-buildpackage, and it links to the
.orig.tar.gz and debian.tar.gz files, which will be downloaded
automatically by dget).

> the upstream git repo (https://github.com/wp-cli/wp-cli) is not in the
> layout used by debpear once it extracts the pear package tgz (this is
> not in the pear.php.net channel so i fed the tarball downloaded via
> pear download wp-cli.github.com/pear/wpcl
> to debpear for the initial debian/ folder setup) so i can't simply fork it
> and add the work-in-progress debian/ folder to my fork - shall i just
> create a git repo with the full tree - unpacked upstream tgz and debian
> folder - i have on my working dir now?

I would advise you to read this:

and do what is advised there. I wrote that page, feel free to be critic
about it, and ask me to rewrite parts of it if you don't understand some
of it.

Extracting the upstream tar.gz in the upstream-sid branch is what I
would do, another way is to do like here (I'm also in the Openstack
packaging team in Debian), which is a very good workflow as well:

what's cool is that it uses upstream git tags.

I hope that helps,


More information about the pkg-php-pear mailing list