[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Fixing 49564 - dependency/BC problem?
From:       Ravikiran Rajagopal <ravi () ee ! eng ! ohio-state ! edu>
Date:       2003-03-09 0:55:54
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,
  KConfigBackEnd::sync() returns nothing, and hence fails silently when the 
user's local config file is not writable. As I understand it, we cannot have 
kdecore dependent on kdeui. So we cannot use a UI element to make the user 
aware of the situation.
  The only alternatives I can think of:

1. Add a sync() function which indicates success or failure - not possible to 
due to BC issues as sync() is virtual. Don't know whether changing a return 
type is BC though.

2. Emit a signal saying it failed, and let the app take care of it. Does not 
help existing binaries, and _all_ apps need to be ported.

3. Add a function canWeSaveConfig(). This has the same problem as #2.

4. If the user's local config file is not writable, try to make it writable. 
Very invasive, and I don't like it.

Should I mark this bug as WONTFIX due to BC issues? If we do make a change and 
#1 is ruled out, my inclination would be for #4. Why would someone outside of 
the kiosk mode make use of read-only config files?

Ravi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+apEabI8Y8y0oVXcRAqeUAJoDeOICL9eu/lvFhYOo+KtvffxE5gCggGG0
aJhRtNF0VdVUDg1SowD+Sw8=
=V6bl
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]