Replicant's stake: Add the real issues

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

1 files changed, 13 insertions, 8 deletions

diff --git a/full-description.md b/full-description.md
index 4ad7e2b..644688b 100644
--- a/full-description.md
+++ b/full-description.md
@@ -63,14 +63,19 @@ build system to handle external projects. Long hours of development time are
 lost due to the incapability of AOSP to detect changes in projects that haven't
 been converted to Blueprint, such as Linux, Mesa or SwiftShader.
 
+Adding and maintaining Blueprint support in all external software components,
+for multiple Android versions, can be incredibly time consuming and could even
+be unsustainable.
+
+More importantly, the future of all Android distributions are very seriously
+threatened by the lack of package manager in the build system. Packages
+definitions typically have a license field. Instead, as Android doesn't use
+packages during the build process, and as all its git repositories checked out
+under a single directory, there is no easy way to keep track of the list of
+licenses that are used.
+
 Replicant is thus seeking to discuss and ultimately decide on a sustainable way
 to go deal with external software components.
 
-Supporting Blueprint could be advantageous for Replicant, due to its faster
-build times, selective recompilation when source files change on disk and
-ability to support multiple Android versions without convoluted conditional
-cases. However it would be preferable if Android supported some form of packages
-similarly to GNU/Linux distributions. Adding and maintaining Blueprint support
-in all external software components can be incredibly time consuming and could
-even be unsustainable.
-
+To really fix the issues, it would be crucial to make if Android support some
+form of packages during the build.
\ No newline at end of file