By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2524

Summary:	Switch from libwv2 to libwv
Product:	TDE	Reporter:	Slávek Banko <slavek.banko>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	CONFIRMED ---
Severity:	major	CC:	bugwatch, slavek.banko
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	All
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:	KOffice

Description Slávek Banko 2015-09-07 15:13:18 CDT

Initial libwv first transformed into libwv2 (http://wvware.sourceforge.net/) to subsequently transformed back into libwv (http://www.abisource.com/projects/). Because libwv2 leaves distributions (Debian Stretch, Ubuntu Wily), therefore would be appropriate to switch to libwv.

Comment 1 Slávek Banko 2015-09-16 20:28:57 CDT

I got the idea to look at how programmers deal with the replacement of the library in the new version of KOffice - Calligra Suite. And I was really surprised - they did nothing - the library was added to the Calligra source code - see https://quickgit.kde.org/?p=calligra.git&a=tree&f=filters%2Fwords%2Fmsword-odf%2Fwv2

How do we deal with the problem?

a) we can do the same - add the library to the KOffice source code

b) we can maintain a separate library - in the build-deps

Note: Adding the library to source code Koffice has the advantage that it will be common for all supported distributions.

Comment 2 Slávek Banko 2015-09-16 20:33:13 CDT

Oh, of course it is still possible:

c) rewrite KOffice code from libwv2 to libwv -  so far I have not evaluated how difficult it would be a change.

Comment 3 Slávek Banko 2015-09-20 08:00:51 CDT

I looked at wv × wv2 closer and now for me are clear differences: wv is 
implemented in C, while wv2 is in C ++. So the differences are quite 
substantial. Since both implementations appear to be without active 
development (wv may have continuation inside AbiWord), it seems pointless to 
do transition wv2 => wv. That's my opinion.

Therefore, I choose for now to maintain a library separately (now concerned to 
Stretch and Wily) and sometime later - after conversion KOffice to CMake, 
could be integrated into KOffice.

Therefore bug is no longer blocking for upcoming release.