| 1 |
remi 08/03/30 20:53:57 |
| 2 |
|
| 3 |
Added: gnome-2.22-upgrade.xml |
| 4 |
Log: |
| 5 |
first go at the Gnome 2.22 Upgrade Guide |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.1 xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml?rev=1.1&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml?rev=1.1&content-type=text/plain |
| 12 |
|
| 13 |
Index: gnome-2.22-upgrade.xml |
| 14 |
=================================================================== |
| 15 |
<?xml version="1.0" encoding="UTF-8"?> |
| 16 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 17 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml,v 1.1 2008/03/30 20:53:57 remi Exp $ --> |
| 18 |
|
| 19 |
<guide link="/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml"> |
| 20 |
|
| 21 |
<title>Gnome 2.20 Upgrade Guide</title> |
| 22 |
<author title="Author"> |
| 23 |
<mail link="remi@g.o">Rémi Cardona</mail> |
| 24 |
</author> |
| 25 |
|
| 26 |
<abstract> |
| 27 |
This is a guide for upgrading from GNOME 2.20.x to GNOME 2.22.x. |
| 28 |
</abstract> |
| 29 |
|
| 30 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
<version>1.0</version> |
| 35 |
<date>2008-03-30</date> |
| 36 |
|
| 37 |
<chapter> |
| 38 |
<title>Changes</title> |
| 39 |
<section> |
| 40 |
<title>Seahorse key manager</title> |
| 41 |
<body> |
| 42 |
|
| 43 |
<p> |
| 44 |
Starting with 2.22, Seahorse (app-crypt/seahorse) is the blessed key and |
| 45 |
password manager, replacing the old and tired Gnome Keyring Manager |
| 46 |
(gnome-extra/gnome-keyring-manager). It handles both GPG and SSH keys, and can |
| 47 |
be also used to manage the passwords saved in your Gnome keyring. |
| 48 |
</p> |
| 49 |
|
| 50 |
</body> |
| 51 |
</section> |
| 52 |
<section> |
| 53 |
<title>PAM and Gnome Keyring integration</title> |
| 54 |
<body> |
| 55 |
|
| 56 |
<p> |
| 57 |
Starting with Gnome 2.20, Gnome Keyring (gnome-base/gnome-keyring) started |
| 58 |
providing a PAM module (pam_keyring.so) to automatically unlock your keyring as |
| 59 |
you log in to your session, thereby saving you the trouble from typing two |
| 60 |
passwords. |
| 61 |
</p> |
| 62 |
|
| 63 |
<p> |
| 64 |
In Gnome 2.22, this feature is now even more easily configured, thanks to |
| 65 |
sys-auth/pambase that sports a shiny gnome use flag. With this flag enabled, |
| 66 |
the pam configuration files in /etc/pam.d/ will automatically have |
| 67 |
pam_keyring.so inserted in the right places. Just remember to use "etc-update" |
| 68 |
or "dispatch-conf" after installing pambase to update those files. |
| 69 |
</p> |
| 70 |
|
| 71 |
</body> |
| 72 |
</section> |
| 73 |
<section> |
| 74 |
<title>GDM 2.20 and 2.22</title> |
| 75 |
<body> |
| 76 |
|
| 77 |
<p> |
| 78 |
For a few years, there have been various people kicking around the idea to |
| 79 |
rewrite GDM for a lot of different reasons (maintainability, new features, |
| 80 |
customizations, ...). That rewrite started last summer, and the GDM team |
| 81 |
decided that 2.22 would be based on that new code. |
| 82 |
</p> |
| 83 |
|
| 84 |
<p> |
| 85 |
Unfortunately, that code still is not ready for production use (at the time of |
| 86 |
writing, it is in an alpha stage) so the Gnome release managers decided not to |
| 87 |
include GDM 2.22 for Gnome 2.22, but to ship GDM 2.20 instead. Ubuntu and |
| 88 |
Mandriva are both going to be using GDM 2.20 for their Spring 2008 releases, we |
| 89 |
also decided to include that version in portage. |
| 90 |
</p> |
| 91 |
|
| 92 |
<p> |
| 93 |
During the Gnome 2.23/2.24 testing cycle, we will probably package the new GDM |
| 94 |
if we feel that the featureset is consistent with the old version and that |
| 95 |
migration does not come with too high a price. |
| 96 |
</p> |
| 97 |
|
| 98 |
</body> |
| 99 |
</section> |
| 100 |
<section> |
| 101 |
<title>Other changes</title> |
| 102 |
<body> |
| 103 |
|
| 104 |
<p> |
| 105 |
Please see the <uri link="http://www.gnome.org/start/2.22/notes/en/">GNOME 2.22 |
| 106 |
Release Notes</uri> for what else new is in this major release of GNOME. |
| 107 |
</p> |
| 108 |
|
| 109 |
</body> |
| 110 |
</section> |
| 111 |
</chapter> |
| 112 |
|
| 113 |
<chapter> |
| 114 |
<title>Known Issues</title> |
| 115 |
<section> |
| 116 |
<title>Gnome no longer available as a session option in GDM</title> |
| 117 |
<body> |
| 118 |
|
| 119 |
<p> |
| 120 |
GDM uses the files available in /usr/share/xsessions/* to figure out which desktop environment options the user will be able to select from the "Sessions" menu. |
| 121 |
</p> |
| 122 |
|
| 123 |
<p> |
| 124 |
In Gnome 2.20, the file /usr/share/xsessions/gnome.desktop was installed by GDM, which causes a lot of headaches. For instance, if you want to use another login manager (such as KDM or Entrance) capable of reading .desktop files but still use a Gnome session, you would have to install GDM even if you never used it. |
| 125 |
</p> |
| 126 |
|
| 127 |
<p> |
| 128 |
In Gnome 2.22, that small issue was fixed and the gnome.desktop file is now installed by gnome-base/gnome-session (which is the actual program launched by the login manager to start Gnome). |
| 129 |
</p> |
| 130 |
|
| 131 |
<p> |
| 132 |
The problem is that Portage can sometimes fail to handle file collisions properly (file collisions happen when to packages install the same files) and may delete the gnome.desktop file altogether. To fix the issue, just remerge gnome-base/gnome-session. |
| 133 |
</p> |
| 134 |
</body> |
| 135 |
</section> |
| 136 |
</chapter> |
| 137 |
</guide> |
| 138 |
|
| 139 |
|
| 140 |
|
| 141 |
-- |
| 142 |
gentoo-commits@l.g.o mailing list |
Archives