GENERAL DESCRIPTION
=-=-=-=-=-=-=-=-=-=
See the desktop-profiles(7) man page for a description of how this package 
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 
  quote, it doesn't show the details, and will mess up the metadata file when
  changing it
- 'ssh -X' bug (##344030): 
  Profiles aren't set when logging in and running programs with 'ssh -X', this
  is because the Xsession.d script isn't run.
  
  A general shell-independ solution seems to be impossible (neither ssh itself
  nor PAM provides a way to source shell scripts) so the only possible solution
  would seem to be to adding a shell snippet to the system-wide on-login script
  for each shell-variant, and have that snippet run the profile activation
  script when it detects an 'ssh -X' login.

  For bourne-compatible shells (bash, dash, ksh, pdksh, mksh) this means adding
  a snippet to /etc/profile which in the absence of a /etc/profile.d directory
  can't be done. Since the base-file maintainer refuses to add such a mechanism
  (For more info see /usr/share/doc/base-files/FAQ and bug #345921) we're stuck.
  The file /usr/share/doc/desktop-profiles/examples/profile-snippet contains the 
  necessary snippet, adding it at the end of /etc/profile will fix this bug for
  all bourne-compatible shells.

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. 

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. 

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 
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

BUILDING KDE-PROFILES
=-=-=-=-=-=-=-=-=-=-=
There is a graphical tool called kiosktool available to aid in the creation 
and maintenance of KDE profiles (regardless of wether they use kiosk 
features). It's available from the testing and unstable archives as the
kiosktool package.

