[debian-edu-commits] debian-edu/ 124/183: Update documentation to reflect that gconf configuration sources managed by desktop-profiles now work by default with the current gconf packages
Alexander Alemayhu
ccscanf-guest at moszumanska.debian.org
Wed Jun 11 16:48:39 UTC 2014
This is an automated email from the git hooks/post-receive script.
ccscanf-guest pushed a commit to branch master
in repository desktop-profiles.
commit 5369ed33c48d344f3da4a550366199a285ecf227
Author: Bart Cornelis <cobaco at linux.be>
Date: Tue Nov 28 17:33:57 2006 +0000
Update documentation to reflect that gconf configuration sources managed by
desktop-profiles now work by default with the current gconf packages
---
README | 65 ++++++++++++++++--------------------------------------
debian/listing | 25 +++++----------------
desktop-profiles.7 | 16 ++++++++------
3 files changed, 33 insertions(+), 73 deletions(-)
diff --git a/README b/README
index aa70d84..5e2d5ce 100644
--- a/README
+++ b/README
@@ -6,7 +6,7 @@ works, and what it does.
KNOWN BUGS
=-=-=-=-=-=
- The profile-manager.kmdr script (i.e. the gui for configuring the metadata
- files doesn't work correctly if the profile description contains a single
+ files) doesn't work correctly if the profile description contains a single
quote, it doesn't show the details, and will mess up the metadata file when
changing it
- 'ssh -X' bug (##344030):
@@ -23,11 +23,9 @@ KNOWN BUGS
shells: bash, dash, ksh, pdksh, mksh, csh, tcsh, zsh, zoidberg, fish and psh.
Where possible the fix is applied automatically (this needs a modularized
on-logon script), otherwise the admin needs to add the required code by hand.
- A Fix for slsh is still missing (if anybody is able to lend a hand please do
- as I'm not familiar with S-lang).
- For bourne-compatible shells (bash, dash, ksh, pdksh, mksh) the system-wide
- on-logon script is /etc/profile. The file
+ For bourne-compatible shells (bash, dash, ksh, pdksh, mksh, posh) the
+ system-wide on-logon script is /etc/profile. The file
/usr/share/doc/desktop-profiles/examples/profile-snippet contains the code
that needs to be added to it in order to fix this bug.
@@ -39,38 +37,21 @@ KNOWN BUGS
(>= 0.96-1) shells don't need to do anything as the system-wide on-logon
script of these shells is modularized, and thus the required code-snippet is
dropped into place on package installation.
-
-GETTING GCONF PROFILES TO WORK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Gconf profiles don't work out-of-the box. The reason for this is that the
-gconf2 package owns the systemwide path file, and assumes you manage all
-configuration sources (the gconf name for profiles) manually by changing it.
-Whereas desktop-profiles assumes you manage them by changing the metadata for
-the profiles.
-
-The desktop-profiles way is more flexible as it allows you to activate
-different profiles active for different sets of users/circumstances.
-Additional benefits are the cross-desktop nature of the desktop-profiles
-mechanism, and the possibility for other packages (and thus Custom Debian
-Distributions, and Debian-derived distributions) to add profiles in a standard
-way without having to mess with the conffile of another package (gconf2).
-
-To get gconf profiles managed by desktop-profiles to work the system-wide
-gconf path file (/etc/gconf/2/path) needs to include the following 2 directives
-'include $(ENV_MANDATORY_PATH)' and 'include $(ENV_DEFAULTS_PATH)' respectively
-before and after any user-controlled sources are included.
-Inclusion of the above two directives is the minimal change needed for
-configuration sources managed by desktop-profiles to work. But only adding
-these directives is suboptimal as it leaves you with 2 ways of managing gconf
-profiles (through desktop-profiles, and by hacking the path file manually).
-What you really want is to have all configuration sources managed by this
-package.
+GCONF PROFILES
+=-=-=-=-=-=-=-=
+The default gconf systemwide path file provided by the gconf2 package only
+includes the minimal changes necessary for using desktop-profiles. That is
+it will only add in the configuration sources managed by desktop-profiles,
+it won't put all configuration sources under desktop-profiles control.
-To facilitate getting there, this package provides a conversion script
-(/usr/sbin/path2listing) that will setup the necessary metadata for all your
-currently used configuration sources, and that will change the systemwide gconf
-path file to the recommended state.
+To facilitate those that want to manage all their gconf configuration sources
+with desktop-profiles this package provides a conversion script
+(/usr/sbin/path2listing) that will parse your current systemwide pathfile,
+generate the necessary metadata for all your currently used configuration
+sources (yes it will recurse into included path files), and change the
+systemwide gconf path file to reflect that all configuration sources will now
+be managed by desktop-profiles.
Running the conversion script doesn't result in any user-visible changes (if it
does there's a bug), still the script will make a backup of the current path
@@ -78,19 +59,11 @@ file before changing it so you can always go back to not managing the gconf
configuration sources with desktop-profiles by simply restoring the path file
backup.
-NOTE FOR DEBIAN-EDU USERS
-=-=-=-=-=-=-=-=-=-=-=-=-=
-Debian-edu users should make sure they have a .listing file with metadata for
-the profiles provided by debian-edu-config. This extra .listing file should be
-placed in /etc/desktop-profiles and should be called debian-edu-config.listing,
-You can download the necessary .listing at
-http://developer.skolelinux.no/~cobaco/desktop-profiles/debian-edu-config.listing
-
GRAPHICAL TOOLS TO USE WHEN BUILDING PROFILES
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- kiosktool (KDE):
Point&Click tool for the creation of KDE-profiles (regardless of wether the
- kiosk, i.e. lockdown, features are used) . It's available from the testing and
+ kiosk, i.e. lockdown, features are used) . Available from the testing and
unstable archives.
- Pessulus (GNOME):
@@ -99,5 +72,5 @@ GRAPHICAL TOOLS TO USE WHEN BUILDING PROFILES
and unstable archives.
- Sabayon (GNOME):
- Point&Click tool for the creation of GNOME-profiles. Not currently in Debian
- though an ITP is filed, see bug #315891.
+ Point&Click tool for the creation of GNOME-profiles. Available from testing
+ and unstable archives.
diff --git a/debian/listing b/debian/listing
index 30160df..70fe0fc 100644
--- a/debian/listing
+++ b/debian/listing
@@ -2,29 +2,14 @@
# profiles in here is to be able to use the default system settings as a
# fallback for anything that isn't defined in activated profiles.
#
-# - In the Debian packages CHOICESPATH (the ROX variable) defaults to
-# $HOME/.rox_choices:/usr/local/share/Choices:/usr/share/rox/Choices
-# (upstream uses $HOME/Choices for the user settings, and /usr/share/Choices
-# for the system settings).
-#
-# -> We split this in user settings and system-settings with the user settings
-# having an very high precedence so they should normally always be used
-# (NOTE: if the ROX profile with the highest precedence isn't writeable
-# there could be problems)
-#
-# NOTE: to activate gnome profiles you need to run the path2listing script
-# included in this package
-#
-# See the desktop-profiles (7) man page for details about the format of this
-# file, and how it will be used
-################################################################################
+# See the desktop-profiles (7) man page for info about the format of this file
kde-prefix;KDE;/usr;;;System-wide kde stuff on Debian (stuff in PREFIX)
-default-xdg_config_dirs;XDG_CONFIG;/etc/xdg;;;Default config location defined by XDG Base Directory Specification
-default-xdg_data_dirs;XDG_DATA;/usr/local/share /usr/share;;;Default data locations defined by XDG Base Directory Specification
+default-xdg_config_dirs;XDG_CONFIG;/etc/xdg;;;Default value as defined by XDG Base Directory Specification
+default-xdg_data_dirs;XDG_DATA;/usr/local/share /usr/share;;;Default value as defined by XDG Base Directory Specification
-default-rox-system;ROX;/usr/local/share/Choices:/usr/share/rox/Choices;;;Default locations for non-user settings of ROX programs on Debian
-default-rox-user;ROX;${HOME}/.rox_choices;999999999999999999;;ROX user settings on Debian (should normally take precedence over everything else)
+default-rox-system;ROX;/usr/local/share/Choices:/usr/share/rox/Choices;;;ROX system settings (on Debian, differs from upstream)
+default-rox-user;ROX;${HOME}/.rox_choices;999999999999999999;;ROX user settings (on Debian, differs from upstream) - should take precedence over everything else
ude-install-dir;UDE;/usr/share/ude;;;Default location of system-wide UDE stuff
diff --git a/desktop-profiles.7 b/desktop-profiles.7
index 473140c..00e8e00 100644
--- a/desktop-profiles.7
+++ b/desktop-profiles.7
@@ -6,24 +6,26 @@ desktop-profiles \- introduction and overview
.SH DESCRIPTION
Desktop-profiles offers a standard way of managing the conditional activation of installed profiles (sets of configuration and/or data files) for the various Desktop Environments in Debian.
.PP
-It currently supports Freedesktop, KDE, XFCE (>= 4.2), ROX, GNUSTEP and UDE out of the box. Support for Gconf (i.e. Gnome) profiles is present but needs a change to the default gconf configuration to be activated (see
-.B "HOW IT WORKS"
-below).
+It currently supports Freedesktop, KDE, Gconf (i.e Gnome), XFCE (>= 4.2), ROX, GNUSTEP and UDE.
.SH HOW IT WORKS
-Each available profile has some metadata associated with it. On X startup an Xsession.d script is run that looks through the metadata for all profiles and activates profiles based on that.
+Each available profile has some metadata associated with it. On X startup an Xsession.d script is run that looks through the metadata for all profiles and activates profiles based on what it finds.
.PP
-Specifically each profile is associated with a set of requirements, and a precedence value. On X startup the Xsession.d script will check for each profile whether the requirements are met, and then activate all those profiles whose requirements are met in order of precedence.
+Specifically each profile is associated with a set of requirements, and a precedence value. On X startup the Xsession.d script will filter out those profiles whose requirements are not met, and then activate the remaining profiles in order of precedence.
.PP
Exactly how a profile is activated depends on the profile kind (you don't need to know this in order to use this package):
.IP \(bu 3
For KDE, Freedesktop, XFCE (>= 4.2), ROX, GNUSTEP and UDE activating profiles is done by setting environment variables: KDEDIRS for KDE, XDG_CONFIG_DIRS and XDG_DATA_DIRS for both Freedesktop and XFCE, CHOICESPATH for ROX, GNUSTEP_PATHLIST for GNUSTEP (usually initialized from the various GNUSTEP_*_ROOT variables) and UDEdir for UDE. With the exception of UDEdir, which takes a single directory, each of these variables takes a precedence ordered list of root-directories (of activated profiles).
.IP \(bu 3
-For GConf profiles two user-specific path files are generated. One containing the activated mandatory "configuration sources", one containing the default "configuration sources" that are activated. At the moment the default system-wide path file doesn't include these automatically, this package provides a script (/usr/sbin/path2listing) that looks at your current configuration and adapts so your configuration sources are controlled by desktop-profiles (see the man page for path2listing o [...]
+For GConf profiles two user-specific path files are generated. One containing the activated mandatory "configuration sources", one containing the default "configuration sources" that are activated.
.IP NOTE:
Environment variables will only be set if their value is different from the default value, and user-specific path files are only generated if the systemwide gconf path file will include them. This to avoid unnecessary clutter.
.IP NOTE:
The above means that for Freedesktop, KDE, GNOME, XFCE (>= 4.2), GNUSTEP and ROX any number of profiles can be activated at the same time. Whereas UDE can only activate 1 profiles at the time.
+.IP NOTE:
+By default the Xsession.d script will assume the metadata files are authoritive, meaning it will ignore any values already assigned to the relevant environment variables.
+.IP NOTE:
+The default system-wide path contains a number of configuration sources not managed by desktop-profiles. In order to facilitate the management of all your configuration sources through desktop-profiles this package provides a script (/usr/sbin/path2listing) that looks at your current gconf configuration and adapts it so your configuration sources are all controlled by desktop-profiles (see the man page for path2listing or the /usr/share/doc/destkop-profiles/README for more information on this).
.SH WHERE TO FIND THE PROFILE METADATA
The metadata is specified in .listing files that are placed in the /etc/desktop-profiles directory. The format of those files is specified in the 'FORMAT OF .listing FILES'-section below.
@@ -45,7 +47,7 @@ Lines containing profile metadata are made up of 6 fields separated by a semi-co
.IP \(bu 3
.B 3th field:
.IP
-Location of the root of the profile directory tree, may contain more then 2 directory (in which case directies should be separated with spaces). Environment variables may be used when specifying root directories (e.g. $HOME/.extra_config).
+Location of the root of the profile directory tree, may contain more then 1 directory (in which case directories should be separated with spaces). Environment variables may be used when specifying root directories (e.g. $HOME/.extra_config).
.IP
Except for Gconf profiles, which use the this field to contain exactly one directive to be included in the generated path file (directives are either \'xml:(readonly|readwrite):<profile-root>\', or \'include <some-path-file>' ).
.IP \(bu 3
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-edu/pkg-team/desktop-profiles.git
More information about the debian-edu-commits
mailing list