Move post-review into a new top-level "rbtools" package

Since the dawn of time, post-review has lived in the Review Board tree, despite being a client script and not necessarily being needed on the server.

This moves post-review into a new rbtools package, which users will be able to easy_install (easy_install -U RBTools). The simplejson dependency will be fetched, and users won't have to go hunting in SVN for a script.

Over time, I'd like to add new scripts into here (such as one to apply a diff from a review request), and further down the road I'd like to create an "rbapi" (or something) package that contains a Python API for talking to a Review Board server, which rbtools (and post-review) will then use. For now, the goal is to just get post-review moved over.

Reviewed at http://reviews.review-board.org/r/788/

2 files changed, 27 insertions, 0 deletions

diff --git a/contrib/P4Tool.txt b/contrib/P4Tool.txt
new file mode 100644
index 0000000..d321a72
--- /dev/null
+++ b/contrib/P4Tool.txt
@@ -0,0 +1,2 @@
+P4Win Tools for Review Board
+>>post-review	python	"<Path of post-review goes here>" %C --p4-client $c --p4-port $p		1	0	1	0	0	1	0		0
diff --git a/contrib/README.P4Tool b/contrib/README.P4Tool
new file mode 100644
index 0000000..64d3e32
--- /dev/null
+++ b/contrib/README.P4Tool
@@ -0,0 +1,25 @@
+About P4Tool
+------------
+
+  P4Tool.txt is an extension to P4win that adds support for invoking
+  post-review from the UI.
+
+
+Installation
+------------
+
+  1) Make a copy of P4Tool.txt and modify it for your setup. Specifically,
+     you'll need to replace "<Path of post-review goes here>" with the path to
+     the post-review script on your system.
+
+     If using a compiled post-review.exe, place the path to this file and
+	 remove "python" before the file path.
+
+  2) Import P4Tool.txt into P4win.
+
+
+Usage
+-----
+
+  To post a change for review, right-click on the change and select
+  "post-review".