guedes/pgxn-utils — pull request #26 by theory (2011-11-27 23:37:43+00:00)
Title: README editing.

In response to your request for a proof.

One comment: In most of the example commands, you include the name of the extension. Is it not the case that if you run the tasks in the extension root directory, you don't have to do that? That is, it assumes the current directory? If so, I think that should be spelled-out, as well.

Also, I've noticed that when I do that, `pgxn-utils bundle` puts the zip file in the parent directory. Took me a few minutes to find it. I think it should just be created in the current directory, or else there should be a message saying where to find it. Furthermore, I think that `pgxn release` should know where to find it, too (which, if it was in the current directory, would be simple).

And finally, I suggest you move this file into `docs/pgxn-utils.md` or similar, add a `docfile` key to `provides:pgxn_utils` that points at it, and then make the `README.md` more generic. I'm thinking like [semver](http://api.pgxn.org/src/semver/semver-0.2.3/), where the README has installation and license information, and the `doc/semver.mmd` file is the usage documentation. Thoughts?

Thanks agin for this, looks great!

Oh, one more thing: How about mentioning the integration with the `pgxn` command-line client?