After upgrading to kdesvn-1.2.1 on F9, I noticed that the libkdesvnpart.la file is not part of the upgraded package, rendering the Quanta/kdesvn integration useless.
As this is a feature that I use frequently, is there a configuration change I need to make or another perhaps "compatibility" package I need to use to allow F9's Quanta to continue to use the kde svn features?
Thanks for the input. -Anthony
Anthony Messina wrote:
After upgrading to kdesvn-1.2.1 on F9, I noticed that the libkdesvnpart.la file is not part of the upgraded package, rendering the Quanta/kdesvn integration useless.
As this is a feature that I use frequently, is there a configuration change I need to make or another perhaps "compatibility" package I need to use to allow F9's Quanta to continue to use the kde svn features?
File a bug please... http://bugzilla.redhat.com/
-- Rex
On Thursday 06 November 2008 09:14:27 am Rex Dieter wrote:
File a bug please... http://bugzilla.redhat.com/
Thank you: https://bugzilla.redhat.com/show_bug.cgi?id=470319
Anthony Messina <amessina <at> messinet.com> writes:
As this is a feature that I use frequently, is there a configuration change I need to make or another perhaps "compatibility" package I need to use to allow F9's Quanta to continue to use the kde svn features?
It's an expected side effect of the upgrade to KDE 4 kdesvn.
That sort of migration pain is going to happen until everything gets ported.
Kevin Kofler
On Thursday 06 November 2008 11:48:04 am Kevin Kofler wrote:
It's an expected side effect of the upgrade to KDE 4 kdesvn.
this much i figured.
That sort of migration pain is going to happen until everything gets ported.
unfortunately, it looks like the quanta migration isn't about to happen any time soon. are there any other kde4 project management-like pieces of software that i could drop in for quanta in its absence in kde4? i used to to use bluefish prior to quanta, but then i switched.