summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJuergen Borleis <jbe@pengutronix.de>2016-06-20 11:23:32 +0200
committerMichael Olbrich <m.olbrich@pengutronix.de>2016-06-20 15:05:03 +0200
commitaeb7ace5a5944daebe09076b9ca4d060ee9c3a58 (patch)
treee87731c84c2aa2d84965ed9ea5bd3965cea04ab6
parent658155f6fb2e0ce36da74b51d112a1645026b106 (diff)
downloadptxdist-aeb7ace5a5944daebe09076b9ca4d060ee9c3a58.tar.gz
Add info about the last and final check for a new package
After this check, the new package is ready for mainline. Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
-rw-r--r--doc/dev_manual.rst21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
index 10cc6ce..f907ea1 100644
--- a/doc/dev_manual.rst
+++ b/doc/dev_manual.rst
@@ -694,6 +694,27 @@ To check it right away, we simply run these two commands:
[...]
+.. important:: Discover somehow hidden dependencies with one more last check!
+
+Up to this point all the development of the new package was done in an already
+built BSP. Doing so sometimes somehow hidden dependcies cannot be seen:
+everything seems fine, the new package builds always successfully and the
+results are working on the target.
+
+So to check for this kind of dependencies there is still one more final check
+todo (even if its boring and takes time):
+
+::
+
+ $ ptxdist clean
+ [...]
+ $ ptxdist targetinstall foo
+ [...]
+
+This will re-start with a **clean** BSP and builds exactly the new package and
+its (known) dependecies. If this builds successfully as well we are really done
+with the new package.
+
Advanced Rule Files
~~~~~~~~~~~~~~~~~~~