summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add WIP FAQGNUtoo/faq-wipDenis 'GNUtoo' Carikli2019-12-111-0/+10
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Replicant's stake: Add the real issuesDenis 'GNUtoo' Carikli2019-12-111-8/+13
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* build system internals: Mention the effort required to add convert to BlueprintDenis 'GNUtoo' Carikli2019-12-111-1/+1
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* build system internals: Linux doesn't use Android libcDenis 'GNUtoo' Carikli2019-12-111-5/+4
| | | | | | The Linux kernel doesn't use a libc to be built. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* build system internals: Explain where the binaries are installedDenis 'GNUtoo' Carikli2019-12-111-1/+2
| | | | | | | | | This improves clarity as in the GNU/Linux case we can create images by extracting the packages content, whereas in Android the build output ends up in a directory that is then used to build the image. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Building: Insist on the build system package managerDenis 'GNUtoo' Carikli2019-12-111-8/+11
| | | | | | | | | | | | | | | | | Not having user installable packages is not the main concern. What creates most of the issues is that no packages are used during the image build process. Because of that: - We cannot use any software build system (autotools) - We don't have clear information on licensing Though having a package manager usable by the user would also bring many benefits. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Replace titleRicardo 'Grim' Cabrita2019-12-021-2/+2
|
* Rework abstract.dllud2019-12-021-3/+7
|
* Rework of full description.dllud2019-12-021-12/+72
|
* Initial draftRicardo 'Grim' Cabrita2019-12-013-0/+444