Hello, >I'm not sure. This is why I suggested a separate version which could be >marked as conflicting with the existing verison. This would at least guarantee >that existing reverse dependencies wouldn't break. I realize now that this >probably isn't a simple as it sounds. >If it's an ABI change, that can be handled, but I'm worried about >non-ABI-related behavior changes breaking existing packages. I can try >to test for some of those issues, but as I'm not familiar with any of the >reverse dependencies, I'm concerned I may miss edge cases. > >That said, I'll look into it and see what I can figure out.
we can separate the library in two binaries, as you suggested, and let current packages choose their best flavour (so, no transition would be needed). I did add "-DBUILD_DEFINES=PUGIXML_WCHAR_MODE" and the resulting library was using wchar, so the change to enabled it is trivial. Unfortunately I don't really speak cdbs, so I don't really know what to change to enable double builds, but since the package is on salsa.debian.org/debian namespace, everybody is free to commit and push in unstable, (Jonas even asked me on irc to co-maintain the package), so as long as you push in experimental, and check reverse-dependencies, I don't see troubles in fixing this bug! thanks in advance for caring! Gianfranco
