From f3199edaf8802e2a59fed2f83e825e09b9d4bd0d Mon Sep 17 00:00:00 2001 From: Vadim Zhukov Date: Wed, 8 Jan 2020 13:09:27 +0300 Subject: mention lack of up-to-date dependencies explicitly [skip ci] Requested by scivision@ --- docs/markdown/Wrap-dependency-system-manual.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/markdown/Wrap-dependency-system-manual.md b/docs/markdown/Wrap-dependency-system-manual.md index cd10a11..caad9b0 100644 --- a/docs/markdown/Wrap-dependency-system-manual.md +++ b/docs/markdown/Wrap-dependency-system-manual.md @@ -6,7 +6,9 @@ on ones that do not have a built-in package manager. The latter problem has been worked around by having third party package managers. They are not really a solution for end user deployment, because you can't tell them to install a package manager just to use your app. On these -platforms you must produce self-contained applications. +platforms you must produce self-contained applications. Same applies +when destination platform is missing (up-to-date versions of) your +application's dependencies. The traditional approach to this has been to bundle dependencies inside your own project. Either as prebuilt libraries and headers or -- cgit v1.1