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:32 +0000 (UTC) [thread overview]
Message-ID: <1385024410.069af8590e30d2760c1e9bddfb95dda122987896.dol-sen@gentoo> (raw)
commit: 069af8590e30d2760c1e9bddfb95dda122987896
Author: W. Trevor King <wking <AT> tremily <DOT> us>
AuthorDate: Sat Feb 9 20:40:33 2013 +0000
Commit: Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Thu Nov 21 09:00:10 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=069af859
doc/HOWTO.txt: Explain how to run catalyst without installing
Thanks to Chris White for explaining this to me.
Reviewed-by: Matt Turner <mattst88 <AT> gmail.com>
---
doc/HOWTO.txt | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
index ea9c8f4..5717f80 100644
--- a/doc/HOWTO.txt
+++ b/doc/HOWTO.txt
@@ -202,3 +202,18 @@ and `dd`:
replacing `X` with the appropriate drive letter for your USB disk.
See https://bugs.gentoo.org/show_bug.cgi?id=251719[bug 251719] for
details.
+
+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:
+
+ # ./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
+directory:
+
+ sharedir="/home/wking/src/catalyst"
next 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=1385024410.069af8590e30d2760c1e9bddfb95dda122987896.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