From: "Brian Dolbec" <brian.dolbec@gmail.com> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/catalyst:master commit in: /, doc/ Date: Wed, 2 Apr 2014 20:09:22 +0000 (UTC) [thread overview] Message-ID: <1396469055.773ae7f9ee04cedba218a9abdc9f9b7e8360f055.dol-sen@gentoo> (raw) 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}"
WARNING: multiple messages have this Message-ID (diff)
From: "Brian Dolbec" <brian.dolbec@gmail.com> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/catalyst:pending commit in: /, doc/ Date: Wed, 2 Apr 2014 20:09:44 +0000 (UTC) [thread overview] Message-ID: <1396469055.773ae7f9ee04cedba218a9abdc9f9b7e8360f055.dol-sen@gentoo> (raw) Message-ID: <20140402200944.Pd89e86rVdP0DwYdQFM6hAfVWcZx6q4afYWd7bKF4Cs@z> (raw) 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}"
next reply other threads:[~2014-04-02 20:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-02 20:09 Brian Dolbec [this message] 2014-04-02 20:09 ` [gentoo-commits] proj/catalyst:pending commit in: /, doc/ Brian Dolbec -- strict thread matches above, loose matches on Subject: below -- 2011-06-25 18:08 [gentoo-commits] proj/catalyst:master " Sebastian Pipping
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=1396469055.773ae7f9ee04cedba218a9abdc9f9b7e8360f055.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: linkBe 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