diff options
author | Tristan Sloughter <[email protected]> | 2013-09-21 14:37:35 -0500 |
---|---|---|
committer | Tristan Sloughter <[email protected]> | 2013-09-21 14:37:35 -0500 |
commit | 4eb9311016cb9a885694819acdc22816186fce59 (patch) | |
tree | 872fd476fa97f4b62d090cd27c8eb05c706c5d44 /overview | |
parent | d74834732981b416209eb3f6739b630e9904f14e (diff) | |
download | relx-4eb9311016cb9a885694819acdc22816186fce59.tar.gz relx-4eb9311016cb9a885694819acdc22816186fce59.tar.bz2 relx-4eb9311016cb9a885694819acdc22816186fce59.zip |
fix highlighting
Diffstat (limited to 'overview')
-rw-r--r-- | overview/index.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/overview/index.md b/overview/index.md index 66e1a5f..c00ac71 100644 --- a/overview/index.md +++ b/overview/index.md @@ -16,6 +16,7 @@ work in package management systems. So lets look at an example. Lets say that you have the following OTP Applications +{% highlight erlang %} app1-1.2 with dependencies app2 @@ -39,26 +40,30 @@ Lets say that you have the following OTP Applications with dependencies app3 app7-2.0 +{% endhighlight %} This is the world of OTP Apps your Relx knows about (basically OTP Apps in the Library Directories you have specified). You have set a config that looks like the following: +{% highlight erlang %} {release, {awesome_supercool, "1.0"}, [{app1, "1.3", '>='}, {app2, "2.0", '>'}, app3]} +{% endhighlight %} When the Relx process has run you will end up with a complete release as follows +{% highlight erlang %} {release, {awesome_supercool, "1.0"}, [{app1, "1.3"}, {app2, "2.1"}, {app3, "2.0"}, {app6, "1.0"}, {app7, "2.0"}]} - +{% endhighlight %} As you can see that is a fully realied view of your direct and transative dependencies based on the world that Relx knows about and the constraints that you specified in your configuration. |