Skip to content

Commit

Permalink
Clarify that user must be running Bash.
Browse files Browse the repository at this point in the history
  • Loading branch information
aevernon committed Jul 1, 2012
1 parent c9375d7 commit f012b62
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ operate on, which right now is always a project name.
Installation
============

peg is so far a single script that doesn't rely on anything else. You
peg is so far a single script; its only dependency is Bash. You
can just copy or link it to any directory that's in your path, such
as /usr/local/bin for a system-wide install. Here's a sample
installation that checks out a working copy and then
Expand All @@ -65,7 +65,7 @@ Creating a first project
The easiest way to make peg work is to create a $HOME/pgwork directory and
let peg manage the whole thing for you::

# git repo setup example
# git repo setup example (you must be running bash)
cd
mkdir -p pgwork
peg init test
Expand Down

0 comments on commit f012b62

Please sign in to comment.