On Mon, 2003-03-10 at 08:48, Jean-Michel Dault wrote:
> Le lun 10/03/2003 � 10:45, Buchan Milne a �crit :
> 
> > > - 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.
> > Maybe rather choose a different screensaver, xscreensaver with flag?
> > This would mean though that we need to get at least one more KDE
> > screensaver in ...
> 
> I actually like krozat a lot, you can create easily a slideshow, but the
> images path and colors are hardcoded into the binary. But we could
> always modify it and ship a new one as /usr/bin/oemdesktop.kss for
> example.
> 
> > > - kdesktop_links is in kdebase, while it's really a script, and could be
> > > contained in mandrake_desk or similar package for easy replacement.
> > Or, rather be made (ala /etc/profile.d, /etc/xinit.d etc) for extension.
> 
> Not much to extend =) But we could modify it so it reads
> /usr/share/oemdesktop/kdesktop_links it it exists.
> 
> > > And we have to find out what to do with upgrades, so that new packages
> > > will not overwrite the user's theme.
> > With the new KDE kiosk framework, this should not be necessary anymore?
> 
> I mean, there's ksplash, the program icons, the user icons, the default
> backgrounds, etc. We must not use any of those if we want to customize
> them, but we must put them in a special path, since they will be
> overriten by RPM when the user upgrades KDE, etc.
> 
> 
> Jean-Michel

Jean-Michel 

   It almost sounds like something along the lines of what is done with
pcmcia is needed.  In that you have the stock config file and you can
add your own custom config files that override the default (or augment) 
So when the user customizes their setup the file say user.conf (or any
name you care to give it) is created.  Now this file is never included
in the rpm and only generated and or read if it is there or the user
does do some kind of creation.  (God I hope I'm being clear here.) Then
anytime you upgrade the stock conf gets overwritten but the users custom
one doesn't.... 

James

> 


Reply via email to