cadey
/
propellor
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge branch 'joeyconfig'

This commit is contained in:
Joey Hess 2015-03-22 10:21:52 -04:00
parent fe7b1233f4 f58d1e5ffe
commit e110a303c5
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/components.mdwn
View File

@ -13,6 +13,8 @@ components.
will put the command in `~/.cabal/bin/propellor`. This propellor command will put the command in `~/.cabal/bin/propellor`. This propellor command
is just a wrapper; it builds and runs what you have set up in `~/.propellor/` is just a wrapper; it builds and runs what you have set up in `~/.propellor/`
## full repository
Typically, the `~/.propellor/` git repository is set up by running the Typically, the `~/.propellor/` git repository is set up by running the
propellor command, or by [[cloning propellor|install]]. That makes propellor command, or by [[cloning propellor|install]]. That makes
the repository contain the full source code to propellor, including the repository contain the full source code to propellor, including
@ -23,6 +25,8 @@ Don't like how a property works, or need to make it more general? Just edit
then copy in `~/.propellor/src/Propellor/` and it will be used. See then copy in `~/.propellor/src/Propellor/` and it will be used. See
[[contributing]] if you want to send your improvements back. [[contributing]] if you want to send your improvements back.
## minimal config repository
All that really needs to be in `~/.propellor/` though, is a `config.hs` All that really needs to be in `~/.propellor/` though, is a `config.hs`
file, and a cabal file. To use propellor this way, you can first file, and a cabal file. To use propellor this way, you can first
install propellor, and then copy the two files from the install propellor, and then copy the two files from the