aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSilvio Rhatto <rhatto@riseup.net>2014-06-13 14:15:15 -0300
committerSilvio Rhatto <rhatto@riseup.net>2014-06-13 14:15:15 -0300
commit1199b177c6d5ab254e974b6f7cd2fdfca6889ee1 (patch)
tree575cd94964b69794b55823cebd7c711de4b1006a
parent57a80f9e4a5c1580015711b4c42fcce6908fc474 (diff)
downloadmetadot-1199b177c6d5ab254e974b6f7cd2fdfca6889ee1.tar.gz
metadot-1199b177c6d5ab254e974b6f7cd2fdfca6889ee1.tar.bz2
Check the source
-rw-r--r--README.mdwn12
1 files changed, 10 insertions, 2 deletions
diff --git a/README.mdwn b/README.mdwn
index 66ea66e..99e258c 100644
--- a/README.mdwn
+++ b/README.mdwn
@@ -17,7 +17,12 @@ Instalation
Get the code:
- git clone git://git.sarava.org/metadot.git
+ git clone git://git.sarava.org/metadot.git && cd metadot
+
+Then check the source integrity of the latest release:
+
+ tag="`git describe --abbrev=0 --tags`"
+ git tag -v $tag && git checkout $tag
Save the metadot repository anywhere but make sure it's available in your `$PATH`.
I'm my config I use `~/apps/metadot`.
@@ -27,7 +32,10 @@ Then get some modules. You can get the whole standard module bundle with
metadot clone git://git.sarava.org/rhatto/dotfiles.git
Modules names as `dotfiles` have a special meaning and are handled like bundles
-and are cloned directly as `~/.dotfiles`.
+and are cloned directly as `~/.dotfiles`. After cloning, you can check the current
+dotfiles revision using
+
+ metadot version
Third-party bundles will hardly suit your needs, so you can fetch individual
modules: