[oe-commits] org.oe.packaged-staging docs/packaged-staging.xml: more bits

[koen commit]

docs/packaged-staging.xml: more bits

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

#
# mt diff -rf1b6b0ac95d6e1640ed0b572df5804fe87003df3 -r350fd527f3d9903d4fee90c7bd1bb3dadb4e8fd8
#
# 
# 
# patch "docs/packaged-staging.xml"
#  from [a769dff9ee283d18b0eb24bddd09f8d415c184f9]
#    to [c161ebf69317597bceba81a30a8654d041d57950]
# 
============================================================
--- docs/packaged-staging.xml	a769dff9ee283d18b0eb24bddd09f8d415c184f9
+++ docs/packaged-staging.xml	c161ebf69317597bceba81a30a8654d041d57950
@@ -305,7 +305,7 @@ Stuffing all archs in the ipkg.conf is w
 Stuffing all archs in the ipkg.conf is wrong as well, since it could allow installing of x86 stuff in an ARM based staging. I have no real solution for that yet.
 </para>
 <para>
-The hardcoded use of ipkg sucks, but it's the only package format OE can generate reliably. Using checkinstall would solve that, but that would introduce even more bootstrap and self-hosting problems.
+The hardcoded use of ipkg sucks, but it's the only package format OE can generate reliably. Using checkinstall would solve that, but that would introduce even more bootstrap and self-hosting problems since we'd need more tools before even starting to think about starting a build.
 </para>
 
 </section>