Deleted all the most obvious pygame components

Author: inclement

README.md

@@ -88,26 +88,23 @@ Please refer to the LICENSE file.
 ## History
 
 In 2015 these tools were rewritten to provide a new, easier to use and
-extend interface. If you are looking for the old toolchain with
-distribute.sh and build.py, it is still available at
-https://github.com/kivy/python-for-android/tree/old_toolchain, and
-issues and PRs relating to this branch are still accepted. However, the
-new toolchain contains all the same functionality via the built in
-pygame bootstrap.
-
-In the last quarter of 2018 the python recipes has been changed, the new recipe
-for python3 (3.7.1) has a new build system which has been applied to the ancient
-python recipe, allowing us to bump the python2 version number to 2.7.15. This
-change, unifies the build process for both python recipes, and probably solve
-some issues detected over the years, but unfortunately, this change breaks the
-pygame bootstrap (in a near future we will fix it or remove it). Also should be
-mentioned that the old python recipe is still usable, and has been renamed to
-`python2legacy`. This `python2legacy` recipe allow us to build with a minimum
-api lower than 21, which is not the case for the new python recipes which are
-limited to a minimum api of 21. All this work has been done using android ndk
-version r17c, and your build should success with that version...but be aware
-that the project is in constant development so...the ndk version will change
-at some time.
+extend interface. If you'd like to browse the old toolchain, its
+status is recorded for posterity at at
+https://github.com/kivy/python-for-android/tree/old_toolchain.
+
+In the last quarter of 2018 the python recipes has been changed, the
+new recipe for python3 (3.7.1) has a new build system which has been
+applied to the ancient python recipe, allowing us to bump the python2
+version number to 2.7.15. This change, unifies the build process for
+both python recipes, and probably solve some issues detected over the
+years. Also should be mentioned that the old python recipe is still
+usable, and has been renamed to `python2legacy`. This `python2legacy`
+recipe allow us to build with a minimum api lower than 21, which is
+not the case for the new python recipes which are limited to a minimum
+api of 21. All this work has been done using android ndk version r17c,
+and your build should success with that version...but be aware that
+the project is in constant development so...the ndk version will
+change at some time.
 
 Those mentioned changes has been done this way to make easier the transition
 between python3 and python2. We will slowly phase out python2 support