| |||||||||||||
GNOME Shell to support a "classic" modeGNOME Shell to support a "classic" modePosted Nov 21, 2012 19:19 UTC (Wed) by Zizzle (guest, #67739)In reply to: GNOME Shell to support a "classic" mode by ebassi Parent article: GNOME Shell to support a "classic" mode
> that's an issue you will have to raise with distribution people - I am not one.
Rubbish. You answered the question.
The "apps" (I would argue that nautilus and gnome-panel are not apps but are the desktop) are not parallel installable.
Which was a deliberate choice by you GNOME devs to force the transition to GNOME3. Which is why people are hating on you.
No one cares if the libs are - I want a the login manager to give me the choice of logging into GNOME2 or GNOME3.
I want to use your code! I just want the choice on which version. I don't want the latest buggy incomplete version. I want to chose when I make the transition.
But I know you guys can't understand how people don't think GNOME3 with no taskbar and no font size changing and no minimize button and 3d hw requirements and no themes and gaudy touch friendly widgets isn't the best thing since sliced bread that everyone should immediately want to switch to.
(Log in to post comments)
GNOME Shell to support a "classic" mode Posted Nov 21, 2012 19:31 UTC (Wed) by ovitters (subscriber, #27950) [Link] The "apps" (I would argue that nautilus and gnome-panel are not apps but are the desktop) are not parallel installable. Jhbuild parallel installs an entire GNOME in your existing distribution. This includes Nautilus and gnome-panel and so on.
GNOME Shell to support a "classic" mode Posted Nov 22, 2012 14:38 UTC (Thu) by Thanatopsis (guest, #14019) [Link]
How is this done? I see nothing in the documentation explaining this.
GNOME Shell to support a "classic" mode Posted Nov 22, 2012 17:31 UTC (Thu) by jspaleta (subscriber, #50639) [Link]
GNOME Shell to support a "classic" mode Posted Nov 22, 2012 19:26 UTC (Thu) by Thanatopsis (guest, #14019) [Link]
Yea, I found that. I don't see any docs on how to do parallel installs of GNOME.
GNOME Shell to support a "classic" mode Posted Nov 22, 2012 20:13 UTC (Thu) by jspaleta (subscriber, #50639) [Link]
you configure jhbuild to install into a directory tree that is non standard. In the examples in the docs that is /opt/gnome/
jhbuild when used to run gnome-session sets up shell environment variables so gnome components use the files installed via the jhbuild process.
If you want to look at specific environment changes you run:
-jef
GNOME Shell to support a "classic" mode Posted Nov 23, 2012 0:12 UTC (Fri) by Thanatopsis (guest, #14019) [Link]
DOH! How did I miss that? Thanks.
GNOME Shell to support a "classic" mode Posted Nov 22, 2012 20:55 UTC (Thu) by ovitters (subscriber, #27950) [Link]
Be warned that if you go the jhbuild route, it'll suck up loads of time before you actually get anything working. The "GNOME OS" bit is not to replace a distro, but to ensure that "GNOME" behaves like an OS.
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:
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).
GNOME Shell to support a "classic" mode Posted Nov 23, 2012 0:39 UTC (Fri) by Thanatopsis (guest, #14019) [Link]
Ok. I've used a tool similar to this in the past when I needed newer GNOME libs so I could build the latest Anjuta on RHEL 4.5. Forget the name of the tool at the moment. I believe it is no longer maintained.
So what is keeping everyone who desires to, from running GNOME 2.x & 3.x side by side?
|
|||||||||||||