Åsmund Grammeltvedt wrote:
On Wednesday 03 October 2007 14:00:58 Andrew Gaffney wrote:
Åsmund Grammeltvedt wrote:
On Wednesday 19 September 2007 18:24:33 Chris Gianelloni wrote:
On Wed, 2007-09-19 at 17:23 +0200, Ã…smund Grammeltvedt wrote:
However, it may just create it with USE=build. Check the
vdb in your stage1 to see what package owns the /root directory.
ccache, apparently. Baselayout _should_ also create /root, but
something seems to go wrong along the way. I guess I should rebuild and
check the logs.
Please do.  If you find it to be an issue with baselayout, please file a
bug so we can get it fixed before we start our next release.
Hm, I haven't had time to actually check if this happens, but the current
theory is this:

Baselayout creates /root, but avoids becoming the owner by
generating /usr/share/baselayout/mkdirs.sh and then running it in
pkg_preinst.

When ccache is unmerged at the end of the stage build, it removes /root,
since its the sole owner.

Does that seem plausible?
Sure, that explanation is very plausible. Since ccache isn't enabled by
default and most of us don't use it for release building, we never would
have seen it. It may even be the reason that wolf31o2 recommends that it
not be used.

In that case, may I suggest the following? :)

-# ccache = enables build time ccache support (highly recommended)
+# ccache = enables build time ccache support (not recommended)

I just tried to reproduce it with a stage3-amd64-2007.0, and I can't. The only reason is that there is a .keep file in /root, which was put there by baselayout's mkdirs.sh script. Unless something has changed with baselayout in the tree since the 2007.0 snapshot, your problem lies elsewhere. Looking at the current stable in the tree (1.12.9-r2), it still does 'kdir /root' unconditionally. Are you using baselayout-2 or something?

--
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
--
[EMAIL PROTECTED] mailing list

Reply via email to