Browse code

Update README.md

Update the really stale README

Nat! authored on 14-09-2017 18:52:25 • GitHub committed on 14-09-2017 18:52:25
Showing 1 changed files
... ...
@@ -38,8 +38,8 @@ shell scripts. If your system can run the bash, it can run **mulle-bootstrap**.
38 38
 
39 39
 ## What it does technically
40 40
 
41
-* fetches [git](//enux.pl/article/en/2014-01-21/why-git-sucks) repositories.
42
-In times of need, it can also checkout [svn](//andreasjacobsen.com/2008/10/26/subversion-sucks-get-over-it/).
41
+* downloads [zip](http://eab.abime.net/showthread.php?t=5025) and [tar](http://www.grumpynerd.com/?p=132) archives
42
+* fetches [git](//enux.pl/article/en/2014-01-21/why-git-sucks) repositories and it can also checkout [svn](//andreasjacobsen.com/2008/10/26/subversion-sucks-get-over-it/).
43 43
 * builds [cmake](//blog.cppcms.com/post/54),
44 44
 [xcodebuild](//devcodehack.com/xcode-sucks-and-heres-why/) and
45 45
 [configure](//quetzalcoatal.blogspot.de/2011/06/why-autoconf-sucks.html)
... ...
@@ -53,32 +53,31 @@ libraries into an "addictions" folder (on participating platforms)
53 53
 
54 54
 So you need a bunch of third party projects to build your own
55 55
 project ? No problem. Use **mulle-bootstrap init** to do the initial setup of
56
-a `.bootstrap` folder in your project directory. Then put the git repository
57
-URLs in a file called `./bootstrap/repositories`:
56
+a `.bootstrap` folder in your project directory. Then add the git repository
57
+URLs:
58 58
 
59 59
 ```
60
-mkdir .bootstrap
61
-echo "# a comment
62
-https://github.com/madler/zlib.git
63
-https://github.com/coapp-packages/expat.git" > .bootstrap/repositories
60
+mulle-bootstrap init
61
+mulle-bootstrap setting -g -r -a "repositories" "https://github.com/madler/zlib.git"
62
+mulle-bootstrap setting -g -r -a "repositories" "https://github.com/coapp-packages/expat.git"
64 63
 mulle-bootstrap
65 64
 ```
66 65
 
67
-**mulle-bootstrap** will check them out into a common directory `.repos`.
66
+**mulle-bootstrap** will check them out into a common directory `stashes`.
68 67
 
69 68
 After cloning **mulle-bootstrap** looks for a `.bootstrap` folder in the freshly
70 69
 checked out repositories. They might have dependencies too, if they do, those
71 70
 dependencies are added and also fetched.
72 71
 
73 72
 Everything should now be in place so **mulle-bootstrap** that can now build the
74
-dependencies with **cmake**. It will place the headers and the produced
73
+dependencies. It will place the headers and the produced
75 74
 libraries into the `dependencies/lib`  and `dependencies/include` folders.
76 75
 
77 76
 
78 77
 ## Tell me more
79 78
 
80 79
 * [How to install](dox/INSTALL.md)
81
-* [How to use](dox/COMMANDS.md)
80
+* [How to use it](dox/COMMANDS.md)
82 81
 * [What has changed ?](RELEASENOTES.md)
83 82
 * [Tweak guide](dox/SETTINGS.md)
84 83
 * [CMakeLists.txt.example](dox/CMakeLists.txt.example) shows how to access dependencies from **cmake**