On Tue, 21 Aug 2007 12:11:20 +0200, Isaac Dupree <[EMAIL PROTECTED]> wrote:
> Jonas Karlsson wrote: >> >> What was the problems? Couldn't it be handled with unmanaged_files? >> > > I mentioned it here... > http://lists.gobolinux.org/pipermail/gobolinux-recipes/2007-July/002044.html > It's still a problem with 1.6.9p4, NO_UNIONFS=yes, if using a sandbox: > > SandboxInstall: unionfs is unavailable. Fallback to FiboSandbox! > SandboxInstall: Installing Sudo... > sudo: can't stat /Programs/Sudo/Settings/sudoers: No such file or directory > Compile: Installation step failed. > > That doesn't look like a normal unmanaged files problem. It works > just fine with UnionSandbox; I don't think sudo even touches those files > in Variable during make install. > No, I found the problem. It's with how we handle the Settings directory and how we try to force the settings to go into Default/Settings of the application. Hopefully we can find a solution to the problem. The responsible code is in SandboxInstall: if ! [ "$unionsandbox" ] then Assert_Dir $default_settings Is_Directory "${settings}" && mv "${settings}" "${settings}.hold" ln -s "${default_settings}" "${settings}" fi which would mean that if we're not using union sandbox, we're moving the current settings away and create a link from $settings_target to $default_settings, so that any write in $target_settings would be redirected to Default/Settings. This produces this error with fibo sandbox, as above, when the installation procedure must use the contents of the Settings directory (with union sandbox the settings are just union mounted ro under the Default/Settings rw mount). Is there another way to solve this, without using union mounts? -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
