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

[Paul Dann]

Hi Lucas,

  I'm afraid I had the same problem again when I installed Scripts 2.6.2
and immediately removed 2.6.0.  Re-symlinking 2.6.2 from the live-cd
solved the problem though it seems, so it might just have been a quirk. 
However, 2.6.2 is having difficulty validating package signatures.  I've
reverted to 2.6.0 for the time being --- I'm doing quite a lot of
installing at the moment.

Hope this helps,
Paul



Lucas C. Villa Real wrote:
> On 1/26/07, André Detsch <detsch at gobolinux.org> wrote:
>   
>> On 1/26/07, Lucas C. Villa Real <lucasvr at gobolinux.org> wrote:
>>     
>>> 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.
>>>       
>> I'm not sure if sourcing /S/L/Env/Cache on Bootscripts makes sense.
>>
>> As I remember, we need to source it anyway inside {bash,zsh}rc (for
>> console login) or xprofile (for kdm/xdm/*dm).
>>     
>
> Indeed, it seems to be useless on Bootscripts.
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gobolinux.org/pipermail/gobolinux-users/attachments/20070126/7375f4fe/attachment-0001.htm