Signed-off-by: Kevin Yap <me@kevinyap.ca>
Kevin Yap authored on 2015/01/09 11:10:59... | ... |
@@ -100,13 +100,13 @@ This is usually difficult for several reasons: |
100 | 100 |
typically don't work well with each other, requiring awkward |
101 | 101 |
custom integrations. |
102 | 102 |
|
103 |
- * Conflicting dependencies. Different applications may depend on |
|
103 |
+ * *Conflicting dependencies*. Different applications may depend on |
|
104 | 104 |
different versions of the same dependency. Packaging tools handle |
105 | 105 |
these situations with various degrees of ease - but they all |
106 | 106 |
handle them in different and incompatible ways, which again forces |
107 | 107 |
the developer to do extra work. |
108 | 108 |
|
109 |
- * Custom dependencies. A developer may need to prepare a custom |
|
109 |
+ * *Custom dependencies*. A developer may need to prepare a custom |
|
110 | 110 |
version of their application's dependency. Some packaging systems |
111 | 111 |
can handle custom versions of a dependency, others can't - and all |
112 | 112 |
of them handle it differently. |