summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorWaldemar Brodkorb <wbx@openadk.org>2014-03-26 11:32:06 (GMT)
committerWaldemar Brodkorb <wbx@openadk.org>2014-03-26 11:32:06 (GMT)
commit3f794fad83e51a090191803aa54f4a7fe0d5a2ef (patch)
tree7f745c03a30bb986995940f1a6354f065803dc53 /docs
parente83010306d2b3f5b788cc6d432856c1b380d6de2 (diff)
remove git as dependency, we now have snapshot tarballs
Diffstat (limited to 'docs')
-rw-r--r--docs/contribute.txt1
-rw-r--r--docs/getting.txt6
-rw-r--r--docs/introduction.txt6
-rw-r--r--docs/patch-policy.txt12
4 files changed, 21 insertions, 4 deletions
diff --git a/docs/contribute.txt b/docs/contribute.txt
index 9092638..5a8e1fd 100644
--- a/docs/contribute.txt
+++ b/docs/contribute.txt
@@ -82,6 +82,7 @@ Here is a short list of details to provide in such case:
* target for which the build fails
* package(s) which the build fails
* the command that fails and its output
+* the make.log file, generated when make v is used
* any information you think that may be relevant
Additionally, you can add the +.config+ file.
diff --git a/docs/getting.txt b/docs/getting.txt
index 534ba99..0902bb6 100644
--- a/docs/getting.txt
+++ b/docs/getting.txt
@@ -5,8 +5,9 @@
Getting OpenADK
---------------
-OpenADK does not have any releases. Only direct Git
-access is possible.
+OpenADK does not have any releases. We are following the
+http://en.wikipedia.org/wiki/Rolling_release[rolling release]
+development model.
To download OpenADK using Git just do:
@@ -20,3 +21,4 @@ Or if you prefer HTTP or using Git behind a proxy:
$ git clone http://git.openadk.org/openadk.git
---------------------
+Or you can get a http://www.openadk.org/snapshots/[snapshot].
diff --git a/docs/introduction.txt b/docs/introduction.txt
index 9917476..3489c9d 100644
--- a/docs/introduction.txt
+++ b/docs/introduction.txt
@@ -24,3 +24,9 @@ processors, MIPS processors, ARM processors, etc.
OpenADK supports numerous processors and their variants; it also comes
with default configurations for some embedded systems and netbooks.
(Raspberry PI, Sharp Zaurus, Lemote Yeelong, IBM X40 and more)
+
+OpenADK is not a Linux distribution and there are no releases or binary
+packages available. If you need something like that, better switch to
+something else. OpenADK builds everything from source. There are only a
+few exceptions to this rule (f.e. some bootloaders and firmware files for
+wireless network cards).
diff --git a/docs/patch-policy.txt b/docs/patch-policy.txt
index b5a585b..e948661 100644
--- a/docs/patch-policy.txt
+++ b/docs/patch-policy.txt
@@ -10,8 +10,8 @@ While integrating a new package or updating an existing one, it may be
necessary to patch the source of the software to get it cross-built within
OpenADK. OpenADK offers an infrastructure to automatically handle this during
the builds. Patches are provided within OpenADK, in the package directory;
-these typically aim to fix cross-compilation, libc support, or other such
-issues.
+these typically aim to fix cross-compilation, libc support, portability issues
+or other things.
Normally the patches are autogenerated via:
------------
@@ -80,3 +80,11 @@ Fetch from: <some url>
It is also sensible to add a few words about any changes to the patch
that may have been necessary.
+
+Upstreaming patches
+~~~~~~~~~~~~~~~~~~~
+
+OpenADK tries to avoid any patches to the source code. If a patch could
+not be avoided, it should be tried to make the patch of a good quality to
+get it upstream. OpenADK tries to report any found issues and try to send
+in any upstream compatible patches.