On Thu, 5 Jul 2001, Ivan E. Moore II wrote: > On Thu, Jul 05, 2001 at 01:46:39PM -0600, Bruce Sass wrote: > > On Thu, 5 Jul 2001, Jens Benecke wrote: > > > On Wed, Jul 04, 2001 at 05:51:36PM -0600, Bruce Sass wrote: <..> > I totally disagree. It's KDE specific and therefore if it's going to be > a conffile it should go into the kde area.
Or you can look at it this way: /etc is for system-wide defaults, *except* /etc/skel which is for per-user defaults. Unless you are planning on setting up a system-wide bookmark file that every user will see, independent of and in addition to fiddling with a USER's .kde directory... ...we are gonna have to just disagree. > > > > Ivan, How about the /etc/skel/... > > > > ...does what we want. > > > > Setting up a default .kde and putting it into /etc/skel has been on my > > todo list for awhile now, but since this is a single real-user machine > > I've had no real pressure to do it (and KDE's default isn't too bad). > > no it does not. it only does part of what we want. However it only takes > care of new users...so all those existing users who have never used kde > before will not be able to take advantage of this. So it is not the > correct solution. Of course it is not the complete solution, there is no way around scripting something to look after pre-existing KDE users (I assumed that is what this whole exercise was about). kde2 vs. skel is a side issue... but it may well turn out to be important if it means the difference between a simple system that requires setup only the first time it is installed, or something more complex that requires continued maintenance. I don't know enough about how KDE sets up an initial $HOME/.kde to determine which is more plausible, and am content top leave it in your capable hands (after voicing and defending my concerns, of course :) - Bruce
