Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
GNOME Shell to support a "classic" mode
Posted Nov 22, 2012 17:31 UTC (Thu) by jspaleta (subscriber, #50639)
Posted Nov 22, 2012 19:26 UTC (Thu) by Thanatopsis (guest, #14019)
Posted Nov 22, 2012 20:13 UTC (Thu) by jspaleta (subscriber, #50639)
If you want to look at specific environment changes you run:
and you can examine the environment variables accordingly.
Posted Nov 23, 2012 0:12 UTC (Fri) by Thanatopsis (guest, #14019)
Posted Nov 22, 2012 20:55 UTC (Thu) by ovitters (subscriber, #27950)
Or in other words: ensure that you can easily join development. Be able to provide people with the latest GNOME release as a VM, including all the various system dependencies which are needed by GNOME. Be able to fully test the whole "OS" (meaning GNOME but also the system dependencies).
To answer your question:
The way that jhbuild does this is by installing everything in different prefix. So instead of /usr, you can have the entire GNOME stack (+ some dependencies) in e.g. $HOME/gnome. You can then tell GDM to launch $HOME/gnome/bin/startgnome.
What I forgot is that this will still share the "dot" files. We've put a lot of work into supporting the XDG directories (~/.config), which can be changed using environment variables. Quite envious of KDE here (they solved that years ago).
Posted Nov 23, 2012 0:39 UTC (Fri) by Thanatopsis (guest, #14019)
So what is keeping everyone who desires to, from running GNOME 2.x & 3.x side by side?
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds