[Konversation-devel] [Bug 141760] please change default logs path

Eike Hein hein at kde.org
Sat Feb 17 03:38:54 CET 2007


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=141760         




------- Additional Comments From hein kde org  2007-02-17 03:38 -------
The previous default path isn't really an option from my POV, it sucks far too much - something like ~/Konversation Logs would be OK, but I'm opposed to changing this prior to the onset of the KDE 4 era for compatibility reasons. The implications for third-party apps for one, but also the implications for users: With the way KConfigXT works, if we change the default path and a user never touched that particular setting, they'll get hit by the change automatically and Konvi will start logging in the other dir, causing confusion and disruption (and yes, I would have been opposed to the last change for the same reason, but I wasn't sitting at the table at the time and it happened, and now it's in 1.0, which is a commitment) unless additional code is written to survey the old dir and copy over its contents. Something for which I don't see any volunteers yet.


> I don't know Beagle, but if its konversation support is appropriate, it should already support the previous path.

The last three public releases of Konversation have used ~/logs, most notably the 1.0 release, but generally all reasonably mature releases of the application. Beagle's Konvi support is recent, and it's no stretch to assume that others have taken note of the 1.0 release as well. That said, I still haven't had time to look at what Beagle is actually doing.


> In general, there is no need for more care than when the path was first changed. 

I strongly disagree and generally vote against changing this for the remaining KDE 3.x releases. We can see about the KDE4 port.


More information about the Konversation-devel mailing list