libtidy.so.5 has removed symbols between 5.2.0 and 5.6.0, but kept SONAME

[oerdnj]

When (exported) symbols are removed from the library it's important for library to bump the SONAME for programs not to break. This hasn't happened and it needs to be done.

I would rather bump the version in a coordinated manner than do that only in Debian.

Excerpts:

+#MISSING: 1:5.6.0-0.1# prvTidyDisplayHTMLTableAlgorithm@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidyNeedsAuthorIntervention@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidyReportAccessWarning@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidyReportError@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidyReportFatal@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidytidyErrorCodeListSize@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidytidyInstalledLanguageListSize@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidytidyLanguageListSize@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# prvTidytidyStringKeyListSize@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetABBR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetALINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetALT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetBGCOLOR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetCHECKED@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetCOLSPAN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetCONTENT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetDATAFLD@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetFOR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetHEIGHT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetHREF@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetHTTP_EQUIV@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetID@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetISMAP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetLANG@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetLANGUAGE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetLONGDESC@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetNAME@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnBLUR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnCLICK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnFOCUS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnKEYDOWN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnKEYPRESS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnKEYUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnMOUSEDOWN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnMOUSEMOVE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnMOUSEOUT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnMOUSEOVER@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetOnMOUSEUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetREL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetROWSPAN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetSELECTED@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetSRC@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetSTYLE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetSUMMARY@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetTARGET@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetTEXT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetTITLE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetTYPE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetUSEMAP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetVALUE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetVLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetWIDTH@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrGetXMLNS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsABBR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsALINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsALT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsBGCOLOR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsCHECKED@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsCOLSPAN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsCONTENT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsDATAFLD@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsFOR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsHEIGHT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsHREF@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsHTTP_EQUIV@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsID@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsISMAP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsLANG@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsLANGUAGE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsLONGDESC@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsNAME@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnBLUR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnCLICK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnFOCUS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnKEYDOWN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnKEYPRESS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnKEYUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnMOUSEDOWN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnMOUSEMOVE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnMOUSEOUT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnMOUSEOVER@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsOnMOUSEUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsProp@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsREL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsROWSPAN@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsSELECTED@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsSRC@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsSTYLE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsSUMMARY@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsTARGET@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsTEXT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsTITLE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsTYPE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsUSEMAP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsVALUE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsVLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsWIDTH@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyAttrIsXMLNS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsA@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsADDRESS@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsAPPLET@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsAREA@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsB@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBASE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBASEFONT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBIG@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBLOCKQUOTE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBODY@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsBR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsCAPTION@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsCENTER@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsCOL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsCOLGROUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDATALIST@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDD@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDIR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDIV@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsDT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsEM@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsEMBED@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsFONT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsFORM@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsFRAME@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsFRAMESET@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH1@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH2@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH3@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH4@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH5@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsH6@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsHEAD@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsHR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsHTML@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsI@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsIFRAME@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsIMG@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsINPUT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsISINDEX@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsLABEL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsLAYER@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsLI@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsLINK@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsLISTING@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsMAP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsMARQUEE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsMENU@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsMETA@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsNOBR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsNOFRAMES@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsNOSCRIPT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsOBJECT@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsOL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsOPTGROUP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsOPTION@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsPARAM@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsPRE@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsU@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsUL@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsWBR@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidyNodeIsXMP@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidySetReportFilter2@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidySetReportFilter3@Base 5.2.0
+#MISSING: 1:5.6.0-0.1# tidySystemLocale@Base 5.2.0

Also if prvTidy means private symbols, you need to use symbol visibility. If the symbol is out there (e.g. exported) it doesn't matter what name you pick: https://gcc.gnu.org/wiki/Visibility (the page says C++, but it should be used for C). In your case it would be easier to use LD Version Script: https://www.gnu.org/software/gnulib/manual/html_node/LD-Version-Scripts.html

[oerdnj]

Since the issue is apparently being ignored here, I am just announcing that the package in Debian will bump the SONAME to libtidy.so.6.

[oerdnj]

Specifically, this is wrong:

    set_target_properties( ${name} PROPERTIES
                                   VERSION   ${LIBTIDY_VERSION}
                                   SOVERSION ${TIDY_MAJOR_VERSION} )

The VERSION and SOVERSION of the library needs to be independent to the version of the sources.

[hosiet]

This issue is being tracked and discussed downstream in Debian right here: https://bugs.debian.org/911130

[geoffmcl]

@oerdnj, @hosiet, all, sorry for the delay... I was hoping a unix person, with more understanding of unix shared libraries, and their .so version, would pick this up...

As suggested, the so called missing tidyAttrIs[name], tidyAttrGet[name], and tidyNodeIs[element] functions were marked as deprecated as far back as about 2008, or before, and alternative API functions given... any package still using them abt 10 years later has to be redone... quite unlikely there would be any package breakage otherwise...

Since its beginning libTidy has used a MACRO, TY_(name)(...) to hide non-public functions... just internally used across objects of the library... these are prefixed with prvTidy, making it clear they are not public functions... they, and the macro, are not included in the published tidy.h header... any package using libTidy should not contain these functions, and deserves to break if they do...

As you may know, the MS Windows compiler/linker handles this hiding by not including them in the important import library, .lib, that accompanies the .dll shared library, through the __declspec(dllimport|dllexport) macro, that is TIDY_EXPORT...

So maybe someone with unix understanding should/could do something similar for a gcc compile/link... they are all declared as TY_(name)...

Given this explanation, is it really necessary to bump the SOVERSION to 6?

Anyway, look forward to more feedback...

[oerdnj]

@geoffmcl Unfortunately, yes, it is needed to bump to SOVERSION and decouple the source version with library version. You cannot rely on marking functions as deprecated as people might still be using them.

I am not well accustomed with cmake, but I can probably make PR to do the library versioning properly if you want. And it should be fairly easy to tweak TIDY_EXPORT for GCC/GNU ld, so it declares the requested symbol visibility also on Linux/Unix.

[oerdnj]

and deserves to break if they do...

While the developer in me agrees with you, the package maintainer screams in horror :)

[hosiet]

Deprecating a function is easy, but removing it would be really costly and you have to bump the SONAME when doing removal to prevent any and every user from encountering missing symbols (missing functions) when using a newer version of library (of the same SONAME.

So the workflow is clear: feel free to deprecate a function, but whenever you remove one (or change API / break ABI), bump the SONAME immediately.

[hosiet]

(BTW: remove function --> soname bump only applies to exported public symbols (functions). If you believe all changes are made on private functions (prvTidy...) then it is not necessary. But you removed tidyAttrIs[name], tidyAttrGet[name], and tidyNodeIs[element] from v5.2 to v5.6 so the soname has to be bumped this time anyway.)

[cmb69]

@oerdnj Would bumping the SONAME to libtidy.so.5.6 be an option? I'm afraid that libtidy.so.6 might cause issues, if there'll ever be an libtidy 6.

[hosiet]

In fact SONAME can only be an (rising) integer, from 0 to 1, 2, 3, ... On Unix-like systems, the programs that are looking for dynamic libraries will only search for something like libfoobar.so.SONAME where SONAME is an integer.

So your proposal is not valid :-/ It's really okay to make the project version and SONAME different and there's already countless examples all around.

[cmb69]

@hosiet Thanks for the explanation!

[oerdnj]

That’s not entirely true, the Debian now has libtidy.so.5deb1 to make room for upstream to use 6 as next. Nevertheless the library soname has to be decoupled from source version. There’s no reason to keep them same.

[geoffmcl]

@hosiet WOW, I am not really the person to be discussing this... The process of creating a libtidy.so link to a libtidy.so.$SOVERSION, which then links to a libtidy.so.${LIBTIDY_VERSION}, which is the actual shared library code, does not apply to Windows native, and while I understand some the history of this, it is just not my cup of tea ;=))

It also seem quite normal for the SOVERSION to be the same as the ${TIDY_MAJOR_VERSION}... yes I can see decoupling them is possible, and experimented with something like -

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 631f0fd..227e1ea 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -405,12 +405,15 @@ if (BUILD_SHARED_LIB)
     if (UNIX AND APPLE)
         set(CMAKE_MACOSX_RPATH 1)
     endif ()
+    if (NOT TIDY_SO_VERSION)
+        set(TIDY_SO_VERSION ${TIDY_MAJOR_VERSION})
+    endif ()
     add_library ( ${name} SHARED ${CFILES} ${HFILES} ${LIBHFILES} )
     set_target_properties( ${name} PROPERTIES 
                                    OUTPUT_NAME ${LIB_NAME} )
     set_target_properties( ${name} PROPERTIES
                                    VERSION   ${LIBTIDY_VERSION}
-                                   SOVERSION ${TIDY_MAJOR_VERSION} )
+                                   SOVERSION ${TIDY_SO_VERSION} )
     set_target_properties( ${name} PROPERTIES 
                                    COMPILE_FLAGS "-DBUILD_SHARED_LIB" )
     set_target_properties( ${name} PROPERTIES 
diff --git a/build/cmake/build-me.sh b/build/cmake/build-me.sh
index 61bdbdd..a3d7317 100755
--- a/build/cmake/build-me.sh
+++ b/build/cmake/build-me.sh
@@ -35,8 +35,9 @@ TMPOPTS=""
 ##############################################
 ### ***** NOTE THIS INSTALL LOCATION ***** ###
 ### Change to suit your taste, environment ###
-TMPINST="/usr"
+TMPINST="$HOME/projects/html_tidy"
 TMPOPTS="$TMPOPTS -DCMAKE_INSTALL_PREFIX=$TMPINST"
+TMPOPTS="$TMPOPTS -DTIDY_SO_VERSION=6"
 ##############################################
 
 ### Accept user argument

This makes it user settable, but is that what we want... some distributions deciding to, and some more carefully weighing this up, and leaving it as we chose, the default ${TIDY_MAJOR_VERSION}... it is compatible to the previous release...

Used this would result in an install as follows, perhaps a little confusing to some -

lrwxrwxrwx 1 geoff geoff      12 Oct 22 20:17 libtidy.so -> libtidy.so.6
lrwxrwxrwx 1 geoff geoff      17 Oct 22 20:17 libtidy.so.6 -> libtidy.so.5.7.16
-rwxrwxr-x 1 geoff geoff 1078624 Oct 22 20:17 libtidy.so.5.7.16

Unfortunately, I do not feel it is the time to bump the ${TIDY_MAJOR_VERSION} to 6... this seems to promise, suggest, some big changes, which are not present in this release... and thus subsequent up to the current next branch... but could be persuaded...

What do others think? I need more feedback... thanks...

But this does not yet address the privTidy functions... changes in the internal arrangement and use of library only functions must not cause this SOVERSION change... ever... so still need a solution to that... maybe we can default to hiding all functions externally, and use the TIDY_EXPORT to make the public API visible... as done in the Windows import library, so this only applies to UNIX, so need so help to do this... patches, PR, etc appreciated...

[ler762]

Unfortunately, I do not feel it is the time to bump the ${TIDY_MAJOR_VERSION} to 6 ...

What if #752 / #754 is included :)

If you need to bump the version to 6 maybe that's enough of an excuse?

It'd be nice if the debian people could take a look at that PR and comment. The interesting bit starts here
#752 (comment)

Yes, I oppose having a ${HOME}/.XXXrc file that can't be over-ridden by a command line option.

[cmb69]

@ler762 Would any of these affect libtidy?

Anyhow, since tidy 5.6.0 had removed some exported symbols, it's already too late to push to 6.0.0.

@geoffmcl See how the export stuff is done in libgd, which might give some ideas for libtidy.