[oe-commits] org.oe.packaged-staging docs/packaged-staging.xml: clear up concerns about p-s + bitbake-mt

[koen commit]

docs/packaged-staging.xml: clear up concerns about p-s + bitbake-mt

Author: koen at openembedded.org
Branch: org.openembedded.packaged-staging
Revision: 87498bc6e8dae7f9a95e0d8ca9d45416a6f50a98
ViewMTN: http://monotone.openembedded.org/revision.psp?id=87498bc6e8dae7f9a95e0d8ca9d45416a6f50a98
Files:
1
docs/packaged-staging.xml
Diffs:

#
# mt diff -r350fd527f3d9903d4fee90c7bd1bb3dadb4e8fd8 -r87498bc6e8dae7f9a95e0d8ca9d45416a6f50a98
#
# 
# 
# patch "docs/packaged-staging.xml"
#  from [c161ebf69317597bceba81a30a8654d041d57950]
#    to [7c33640f3ac25b79c8dff0ae56b35042123ead4e]
# 
============================================================
--- docs/packaged-staging.xml	c161ebf69317597bceba81a30a8654d041d57950
+++ docs/packaged-staging.xml	7c33640f3ac25b79c8dff0ae56b35042123ead4e
@@ -59,7 +59,7 @@ For each to be built package we will rep
 
 <section>
 	<title>Incrementally installing packages</title>
-<para>In contrast to repopluating the staging area from scratch we install additional dependencies and remove conflicting packages. The installing and removing of packages is assumed to be faster than repopulating from scratch. Once a package completed we could consider removing the non-native depends to avoid a growing staging directory. One issue is with the clean task. We could assume that cleaning a package will remove it from the staging area as well. There is one possible problem with it. Let us assume we want to clean quilt-native, virtually every package DEPENDS on it, we would have to clean the staging area completely. If this is the wished behaviour needs to be discussed. This should be safe for a multithreaded bitbake, given that no two do_stages access staging at the same time.
+<para>In contrast to repopluating the staging area from scratch we install additional dependencies and remove conflicting packages. The installing and removing of packages is assumed to be faster than repopulating from scratch. Once a package completed we could consider removing the non-native depends to avoid a growing staging directory. One issue is with the clean task. We could assume that cleaning a package will remove it from the staging area as well. There is one possible problem with it. Let us assume we want to clean quilt-native, virtually every package DEPENDS on it, we would have to clean the staging area completely. If this is the wished behaviour needs to be discussed. This should be safe for a multithreaded bitbake, given that do_stages is the only task running, all other task will have to wait for staging to be complete.
 </para>
 </section>
 </chapter>