[gobolinux-users] [gobolinux-devel] Problems on latest Scripts release

[Lucas C. Villa Real]

On 1/26/07, Paul Dann <giddie at christian.net> wrote:
>
>  Can we ask what it was?  I spent quite a while digging around in there.  I
> even stumbled across a beta copy of the GoboLinux book ;)

Sure. The problem came with a commit where we were trying to make it
possible for Environment files to use $goboVariables. Up to that date,
all Environment files needed either to hardcode entries to the
filesystem, or to source GoboPath.

Since SymlinkProgram creates a unique Cache by concatenating all these
Environment files (which is then sourced by the Bootloader), doing the
latter would end up replicating 'source GoboPath' many times.

So, the original patch added a simple 'source GoboPath' line to the
start of the Cache file generated, plus a bunch of 'unset goboFoo' in
the end of the script, just to avoid having them spread around all
consoles. The problem is that our BootScripts were still making use of
goboVariables after sourcing that Cache, where they started to appear
empty.

The fix was just commited, and consisted of a simple check: if there
were already goboVariables configured at the time the Cache was
called, do not unset them at the end of the file.

-- 
Lucas
powered by /dev/dsp