On 23 Jun 2011, at 20:35, Wichmann, Mats D wrote: > > > On Thu, Jun 23, 2011 at 12:31 PM, Kok, Auke-jan H <[email protected]> > wrote: > On Thu, Jun 23, 2011 at 12:20 AM, Anas Nashif <[email protected]> wrote: > > Why exactly is this link needed anyways > > > uxlaunch is now a generic xsession launcher. It will use the session > files stored in /usr/share/xsessions (and a few other places including > ~/.config/xsessions/) to start up the desktop session, more or less > compatible with gdm, kdm etc. > > Also, the user themselves can both create sessions themselves and > select which session to start at boot time completely independent of > what the distro, or SA has set as global preference. > > The issue is that we need to figure out what the "system" default is > at boot time. Also, the SA needs to be able to override that for all > users, and last, the user needs to be able to override this himself. > > On top of that, in the current state of MeeGo it's impossible to have > packages install "the default setting" since at any given time we will > have multiple potential sessions available.
if I remember correctly even if you had multiple sessions with gdm for example, you could configure one in a 'configuration file' as your desktop, no links were involved. > > Take a look for instance at netbook. As soon as a user installs the > xbmc package, he now has 2 session files. It would be an issue if all > of a sudden his desktop would no longer appear after a reboot, but > something else instead. Then there is a bug either in the netbook or xbmc. > > It also makes no sense to do a package %post, since, for instance, on > netbook, it's quite likely that mcompositor is installed before > mutter, and now your netbook image would start.... god knows what. > > So, I made the choice to switch from: > > `echo "session=/usr/bin/foo" >> /etc/sysconfig/uxlaunch" > > to > > `ln -sf gnome.desktop /usr/share/xsessions/default.desktop` > > which in itself is already better, since we're still allowing the > config file to be used, and the user can override this choice, and > we're not potentially messing up a config file. How is that better beside making it more complex by allowing things to be done in different ways and thus increasing the the risk that 1 type of settings overrides the other leaving the user (What user? Probably the developer) perplexed why he is getting a different desktop (Which he should not have in the first place) > > can you use the alternatives system for this? We do not have this anymore. But, I do not understand why a link on the file system is better than a configuration file, what exactly is the advantage and why do we care about having multiple desktops anyways? _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
