diff options
author | 2014-11-18 10:59:03 +0100 | |
---|---|---|
committer | 2014-11-18 10:59:03 +0100 | |
commit | 7919e0b8f0fc1d7eb8c3b735f53b119583a96a47 (patch) | |
tree | b7f992704c315603fe2913519056e7751de866e8 | |
parent | 0.1.2 release (diff) | |
parent | Better titles (diff) | |
download | gs-elpa-7919e0b8f0fc1d7eb8c3b735f53b119583a96a47.tar.gz gs-elpa-7919e0b8f0fc1d7eb8c3b735f53b119583a96a47.tar.bz2 gs-elpa-7919e0b8f0fc1d7eb8c3b735f53b119583a96a47.zip |
Merge pull request #1 from alem0lars/master
Better titles in the README.md
-rw-r--r-- | README.md | 10 |
1 files changed, 4 insertions, 6 deletions
@@ -1,19 +1,17 @@ This is [g-sorcery](https://github.com/jauhien/g-sorcery) backend for elisp packages. -Installation -====================== +# Installation ``` emerge -va gs-elpa ``` -Usage -====================== +# Usage There are two ways of using **gs-elpa** -** Using gs-elpa with [layman](https://wiki.gentoo.org/wiki/Layman) ** +## Using gs-elpa with [layman](https://wiki.gentoo.org/wiki/Layman) It the the recommend way and I strongly suggest it. @@ -52,7 +50,7 @@ Note, that some overlays may depend on other overlays, in this case you'll need dependencies first (always add the whole gnu-elpa overlay). -** Using gs-elpa as stand-alone tool ** +## Using gs-elpa as stand-alone tool In this case you should create an overlay (see **portage** documentation), sync it and populate it with one or more ebuilds. Then ebuilds could be installed by emerge or by **gs-elpa** tool. |