[Sugar-devel] SoaS v10 testing and a few minor issues with 0.100

[Daniel Narvaez]

On 17 November 2013 23:13, Jerry Vonau <jvonau at shaw.ca> wrote:

> On Sun, 2013-11-17 at 20:28 +0000, Peter Robinson wrote:
> > On Sun, Nov 17, 2013 at 8:22 PM, Jerry Vonau <jvonau at shaw.ca> wrote:
> > > Hi Peter,
> > >
> > > On Sun, 2013-11-17 at 19:33 +0000, Peter Robinson wrote:
> > >> Secondly, a minor annoyance with sugar-runner is that the "shutdown"
> > >> and "reboot" options in the menu should likely be disabled when sugar
> > >> is being run in sugar-runner (leaving just logout) because it takes
> > >> the main desktop with it without any noticed that it might do that.
> > >>
> > >
> > > I believe the view-ability of those are settable in gconf, something
> for
> > > the spin's kickstart file to alter.
> >
> > sugar-runner isn't used in the spin, it's used in the General
> > distribution for those that want to run sugar within another desktop
> > environment whether as an enduser or developer so a kickstart here is
> > completely irrelevant and doesn't even come into play
> >
>
> Forgive me, I thought from the subject that Soas is a livecd based image
> that can be installed build with livecd-creator, using what is more or
> less the same backend that olpc-os-builder uses. The builds are driven
> via kickstart files, with some commands structures shared between the
> two images [1][2] in respect to gconftool-2. While show_logout and
> show_restart keys were configurable before the latest patch[3] extends
> that to shutdown now. While you say those are completely unrelated how
> can that be when the new default in the schema is true, just wondering
> how sugar-runner will deal with the new default going forward, really
> didn't change the behaviour just made it optional. My concern is maybe
> that default needs to be false for sugar-runner leaving others having to
> account for the change, that is all. It doesn't really matter to me
> either way as long as the key becomes set should we need to set it in
> the future.
>
>

Hi,

I'm not sure to understand your concern. We default to true, so keep the
same behavior. sugar-runner will set the environment variables to "no"
disabling the items only for sugar-runner and not when running from gdm.

Can you explain what's the issue exactly?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131117/19d1d525/attachment-0001.html>