Le lun 10/03/2003 � 09:44, Buchan Milne a �crit : > > If you're selling systems, you might want to setup a theme, or stuff > > like that as well. Here's an example of what you could do: > > In /usr/bin/kdesktop-links, add something like: > > That way, it will setup defaults the first time the user logins.
> This kind of stuff needs to be package, IMHO with a GUI, and put on > ProSuite or similar, so that corporates can also do this kind of thing. > draksplash etc are nice, but how about a gui where you just choose your > company logo (for KDM screen, screensaver etc), background (?dm > backgrounds, bootsplash etc), select your template config files, and > generate an RPM? Yes, that's what I plan to do eventually, but there are certain things we need to modify first. - krozat, the screensaver, has hard-coded colors, which is not good if the company logo is not Mandrake blue. Same thing with the Gnome screensaver (Gdadou?), except that it's an XML file. - kdesktop_links is in kdebase, while it's really a script, and could be contained in mandrake_desk or similar package for easy replacement. Would you imagine recompiling kdebase just to add an icon on the desktop? ;-) And we have to find out what to do with upgrades, so that new packages will not overwrite the user's theme. > We have an rpm we use for desktop machines, which on %post does a number > of operations (add urpmi update source, add NFS mounts to fstab, > installs bootsplash theme, and updates many config files). If a company > then also had a urpmi repository (marked as update source), they would > only need to update the rpm, and have the automagic updates (see urpmi > evangelism thread) pull it in the next morning. The Sherbrooke University LUG does basically the same thing. We only have to find out a clean way to do it, and we'll submit it when it's ready. Jean-Michel
