[Bug 1004] networked (not only kde) configs, remaining steps
http://bugs.skolelinux.no/show_bug.cgi?id=1004
------- Additional Comments From cobaco@linux.be 2007-03-01 21:13 -------
As an admin in a school you really don't want to change the profiles
contained in the debian-edu packages directly. Instead you want to create your
own profile and give it a higher priority then the debian-edu ones.
Why do it this way? a couple of reasons:
- you clearly delineate which agent (debian-edu vs local site admin) defined
which settings, and you each have your own playground.
-> no questions on upgrades of "there's local changes to this file, what do
you want to do"
- The local site admin doesn't loose any power what he specifies still goes
(as long as the local site profile has a higher priority then the debian-edu
ones)
As to different kde versions that's not a problem either, if configuration
needs to differ you just create 2 profiles and add a condition that checks the
kde version to the profile meta data (in fact we used to do this in the
debian-edu-config for kde2 vs kde3, as the proxy settings were different, the
condition for such is: $(kde-config --version | grep "^KDE: 3") ).
-> shipping the debian-edu defined packages in debian-edu-config is fine, you
don't want to directly change these anyway.
-> we do want a central place to place the local site profile(s), to achieve
this we need 2 things:
1) decide where to put those profiles (doesn't really matter where as long
as it's accessible on all clients)
3) add a metadata line to the .listing file in debian-edu-config that adds
the decided profile dir with a higher priority then any of our own
profiles.
A local site admin can then just drop the configuration changes he makes into
the local-site configuration directory.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Reply to: