From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4F6131387FD for ; Wed, 2 Apr 2014 20:09:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 78DFCE0DCE; Wed, 2 Apr 2014 20:09:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0FFC7E0DC8 for ; Wed, 2 Apr 2014 20:09:25 +0000 (UTC) Received: from spoonbill.gentoo.org (spoonbill.gentoo.org [81.93.255.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 1FA7833FDD0 for ; Wed, 2 Apr 2014 20:09:24 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by spoonbill.gentoo.org (Postfix) with ESMTP id CA78C18874 for ; Wed, 2 Apr 2014 20:09:22 +0000 (UTC) From: "Brian Dolbec" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Brian Dolbec" Message-ID: <1396469055.773ae7f9ee04cedba218a9abdc9f9b7e8360f055.dol-sen@gentoo> Subject: [gentoo-commits] proj/catalyst:master commit in: /, doc/ X-VCS-Repository: proj/catalyst X-VCS-Files: doc/HOWTO.txt testpath X-VCS-Directories: / doc/ X-VCS-Committer: dol-sen X-VCS-Committer-Name: Brian Dolbec X-VCS-Revision: 773ae7f9ee04cedba218a9abdc9f9b7e8360f055 X-VCS-Branch: master Date: Wed, 2 Apr 2014 20:09:22 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: 29be8e89-6d8c-4a25-b540-a07a683fb4fa X-Archives-Hash: af0cf5bd143fa7a70deb6347746f4b8d commit: 773ae7f9ee04cedba218a9abdc9f9b7e8360f055 Author: Brian Dolbec gentoo org> AuthorDate: Fri Jan 25 04:26:38 2013 +0000 Commit: Brian Dolbec gmail 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}" From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A197F1387FD for ; Wed, 2 Apr 2014 20:09:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 40E89E0E18; Wed, 2 Apr 2014 20:09:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BAA19E0E11 for ; Wed, 2 Apr 2014 20:09:46 +0000 (UTC) Received: from spoonbill.gentoo.org (spoonbill.gentoo.org [81.93.255.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id E4B7733FDEC for ; Wed, 2 Apr 2014 20:09:45 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by spoonbill.gentoo.org (Postfix) with ESMTP id 98EEB18874 for ; Wed, 2 Apr 2014 20:09:44 +0000 (UTC) From: "Brian Dolbec" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Brian Dolbec" Message-ID: <1396469055.773ae7f9ee04cedba218a9abdc9f9b7e8360f055.dol-sen@gentoo> Subject: [gentoo-commits] proj/catalyst:pending commit in: /, doc/ X-VCS-Repository: proj/catalyst X-VCS-Files: doc/HOWTO.txt testpath X-VCS-Directories: / doc/ X-VCS-Committer: dol-sen X-VCS-Committer-Name: Brian Dolbec X-VCS-Revision: 773ae7f9ee04cedba218a9abdc9f9b7e8360f055 X-VCS-Branch: pending Date: Wed, 2 Apr 2014 20:09:44 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: 0b760be1-18c9-49f3-9c91-977faa65e4ba X-Archives-Hash: 5828ae1d0769494f15e96ff2543486ea Message-ID: <20140402200944.Pd89e86rVdP0DwYdQFM6hAfVWcZx6q4afYWd7bKF4Cs@z> commit: 773ae7f9ee04cedba218a9abdc9f9b7e8360f055 Author: Brian Dolbec gentoo org> AuthorDate: Fri Jan 25 04:26:38 2013 +0000 Commit: Brian Dolbec gmail 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}"