[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     abc30360f3cb0f03e3711cce7d324fa2e14fee0a
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Dec 27 02:59:14 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=abc30360

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 5717f80..178f7fc 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -208,9 +208,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     ce0c63fdff63ff0ac913f1b83dd8e166da7d75d5
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sun Dec 29 18:54:06 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=ce0c63fd

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 5717f80..178f7fc 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -208,9 +208,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     2fbb8ba688d5a2d51fe174b5cc96a0138ac6b01a
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Tue Dec 31 03:58:32 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=2fbb8ba6

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 5717f80..178f7fc 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -208,9 +208,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     f95429878a8944b757df07c25552c9655729ebc4
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Tue Dec 31 04:33:36 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=f9542987

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 5717f80..178f7fc 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -208,9 +208,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     00fe442bae3b9fafb63823146d3c4cff110501c3
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Tue Dec 31 04:40:15 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=00fe442b

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 5717f80..178f7fc 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -208,9 +208,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     a821eefec3ceae4ca11a0ecb097468f64b273c5f
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Tue Dec 31 17:59:07 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=a821eefe

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     08966e8180ec28c9250cd5b3f397528af1023484
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Wed Jan  1 23:55:46 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=08966e81

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     c270303dc801cc36f88da721bc39dc4603fd473e
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Jan  3 04:39:29 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=c270303d

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     dcaf4e53932607d43d521617cc9070e99d7a3757
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Jan  3 05:41:26 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=dcaf4e53

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     188b8053a75399faaa8b4f0fcab979d0feb36ea8
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Jan  3 06:40:03 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=188b8053

Commit my testpath file with instructions

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     1f0f935a6c54a56f3230c7d183ab414ff2ea25f1
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sun Jan 12 20:48:21 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=1f0f935a

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     3a245186937a45e4d50efc7e073e8ee04d12b2f1
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sat Feb 22 18:31:06 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=3a245186

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     5a37f06a9420b6f087cebe1bc2d48165d6ad5e7f
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sat Feb 22 21:43:18 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=5a37f06a

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..0eed300
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your caatalyst git checkout
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     7a5855f32a68cb74b55fc73452ae49130723b292
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sun Mar  2 16:06:53 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=7a5855f3

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 19 +++++++++++++++++++
 2 files changed, 27 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..8394ff6
--- /dev/null
+++ b/testpath
@@ -0,0 +1,19 @@
+
+# When sourced from the same directory as the checkout these 2 paths direct
+# commands use your git checkout in the terminal window you wish to run
+# the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     9d1a35efed78b7eca5ae25003fb53be2ee5e39f8
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Sun Mar  2 22:54:04 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=9d1a35ef

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 19 +++++++++++++++++++
 2 files changed, 27 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..8394ff6
--- /dev/null
+++ b/testpath
@@ -0,0 +1,19 @@
+
+# When sourced from the same directory as the checkout these 2 paths direct
+# commands use your git checkout in the terminal window you wish to run
+# the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config file "test.conf" with similar path changes for it to find
+# and use/run the git checkout code and to store it's data to a test directory
+# it can then be run on a system without being installed or replacing an existing
+# catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c ./test.conf -p  -f stage1.spec
+
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
+
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"

[gentoo-commits] proj/catalyst:pending commit in: /, doc/

[Brian Dolbec]

commit:     773ae7f9ee04cedba218a9abdc9f9b7e8360f055
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 25 04:26:38 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Wed Apr  2 20:04:15 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=773ae7f9

Commit a testpath file to source with instructions on it's use.

Make testpath automagic via dwfeed's tweak
Update HOWTO on how to run the git checkout code directly without being installed.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      | 18 ++++++++++++++++++
 2 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index 8fe63c1..cec22c3 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -233,9 +233,15 @@ Running catalyst from a Git checkout
 
 If you're developing catalyst, you'll want to test your altered
 version.  An easy way to run it without reinstalling is to setup a
-local configuration file and run:
+local configuration file.  The checkout also includes a testpath file
+which when sourced adds it's bin/ to PATH and it's checkout dir to
+PYTHONPATH.  That terminal will then use the checkout bin/catalyst and
+the checkout's python modules.
 
-    # ./catalyst -c catalyst.conf -f path/to/your.spec
+cd into the checkout directory and run:
+
+    # source ./testpath
+    # catalyst -c catalyst.conf -f path/to/your.spec
 
 The local configuration file can use all the defaults except for
 `sharedir`, which you should change to point to your development

diff --git a/testpath b/testpath
new file mode 100644
index 0000000..37af9c9
--- /dev/null
+++ b/testpath
@@ -0,0 +1,18 @@
+
+# edit the following 2 paths to point to your catalyst git checkout if nessecary
+# then in a terminal window you wish to run the git code in...
+# cd ~/catalyst
+# source ./testpath
+# edit a config catalyst.conf file. Make similar path changes for it to
+# find and use/run the git checkout code.
+# The catalyst code can then be run on a system without being installed or
+# replacing an existing catalyst install which may be used for production.
+#
+# then run catalyst from there
+#  eg:
+#
+# catalyst -c catalyst.conf -p -f stage1.spec
+
+export PATH="$(dirname ${BASH_SOURCE[0]})/bin:${PATH}"
+
+export PYTHONPATH="$(dirname ${BASH_SOURCE[0]})${PYTHONPATH:+:}${PYTHONPATH}"