Yes, it was also suggested to check the directories prior to chmod'ing.
But I'm still not so sure about that, or how extensive the checking
should be. Perhaps cleaning out sticky bits more extensively could be
suggested in the documentation.
Alex Franco
On 09/02/2015 04:47 PM, Peter Seebach wrote:
On Wed, 2 Sep 2015 11:36:45 -0500
Alex Franco <[email protected]> wrote:
-chmod -R -st "$BUILDDIR"
+chmod -st "$BUILDDIR"
I was about to say! I just did an update to a version with this, and as it
happens, my build dir also contains about four full copies of tmp-glibc and
sstate-cache corresponding to different versions of pseudo I was comparing
between...
I'd say maybe both $BUILDDIR and $BUILDDIR/conf. Although it might not be a
horrible idea to think about cleaning out sticky bits, because it occurs to
me: pseudo is not stripping the set* bits when writing to the filesystem.
Which means that a build directory can end up containing files owned by the
build user, and setuid, which is maybe a Bad Thing.
... It may be that pseudo should strip those bits from the filesystem.
-s
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
