public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:3.0 commit in: /, doc/
Date: Thu, 21 Nov 2013 09:06:33 +0000 (UTC)	[thread overview]
Message-ID: <1385024411.0b344d4add947ac213852359e097bd82644c0c74.dol-sen@gentoo> (raw)

commit:     0b344d4add947ac213852359e097bd82644c0c74
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Wed Jun  5 17:39:48 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Thu Nov 21 09:00:11 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=0b344d4a

Make testpath automagic via dwfeed's tweak

Update HOWTO to include the testpath use.

---
 doc/HOWTO.txt | 10 ++++++++--
 testpath      |  4 ++--
 2 files changed, 10 insertions(+), 4 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
index 9fd7e45..0eed300 100644
--- a/testpath
+++ b/testpath
@@ -13,6 +13,6 @@
 #
 # catalyst -c ./test.conf -p  -f stage1.spec
 
-export PATH="/home/brian/Dev/git/catalyst/bin:${PATH}"
+export PATH="$(dirname $BASH_SOURCE[0])/bin:${PATH}"
 
-export PYTHONPATH="/home/brian/Dev/git/catalyst/:${PYTHONPATH}"
+export PYTHONPATH="$(dirname $BASH_SOURCE[0]):${PYTHONPATH}"


             reply	other threads:[~2013-11-21  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  9:06 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-21  9:06 [gentoo-commits] proj/catalyst:3.0 commit in: /, doc/ Brian Dolbec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1385024411.0b344d4add947ac213852359e097bd82644c0c74.dol-sen@gentoo \
    --to=brian.dolbec@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox