Gentoo Archives: gentoo-catalyst

From: Brian Dolbec <dolsen@g.o>
To: gentoo-catalyst@l.g.o
Subject: [gentoo-catalyst] [PATCH] Commit a testpath file to source with instructions on it's use.
Date: Sun, 02 Mar 2014 23:07:12
Message-Id: 1393801623-13968-1-git-send-email-dolsen@gentoo.org
1 Make testpath automagic via dwfeed's tweak
2 Update HOWTO on how to run the git checkout code directly without being installed.
3 ---
4 doc/HOWTO.txt | 10 ++++++++--
5 testpath | 19 +++++++++++++++++++
6 2 files changed, 27 insertions(+), 2 deletions(-)
7 create mode 100644 testpath
8
9 diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
10 index 8fe63c1..cec22c3 100644
11 --- a/doc/HOWTO.txt
12 +++ b/doc/HOWTO.txt
13 @@ -233,9 +233,15 @@ Running catalyst from a Git checkout
14
15 If you're developing catalyst, you'll want to test your altered
16 version. An easy way to run it without reinstalling is to setup a
17 -local configuration file and run:
18 +local configuration file. The checkout also includes a testpath file
19 +which when sourced adds it's bin/ to PATH and it's checkout dir to
20 +PYTHONPATH. That terminal will then use the checkout bin/catalyst and
21 +the checkout's python modules.
22
23 - # ./catalyst -c catalyst.conf -f path/to/your.spec
24 +cd into the checkout directory and run:
25 +
26 + # source ./testpath
27 + # catalyst -c catalyst.conf -f path/to/your.spec
28
29 The local configuration file can use all the defaults except for
30 `sharedir`, which you should change to point to your development
31 diff --git a/testpath b/testpath
32 new file mode 100644
33 index 0000000..8394ff6
34 --- /dev/null
35 +++ b/testpath
36 @@ -0,0 +1,19 @@
37 +
38 +# When sourced from the same directory as the checkout these 2 paths direct
39 +# commands use your git checkout in the terminal window you wish to run
40 +# the git code in...
41 +# cd ~/catalyst
42 +# source ./testpath
43 +# edit a config file "test.conf" with similar path changes for it to find
44 +# and use/run the git checkout code and to store it's data to a test directory
45 +# it can then be run on a system without being installed or replacing an existing
46 +# catalyst install which may be used for production.
47 +#
48 +# then run catalyst from there
49 +# eg:
50 +#
51 +# catalyst -c ./test.conf -p -f stage1.spec
52 +
53 +export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
54 +
55 +export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"
56 --
57 1.8.5.3

Replies