It is named libBotan rather than libbotan but it exposes the same symbols.. is it possible to simply drop it and make it use a system copy, please?
Hmm. Interesting. qt-creator fails to build with botan-1.10.1 so it needs to hardcode 1.8.* version. Even if I don't like forcing users to use a specific version, this is the right way to go
An initial ebuild was pushed to qting-edge overlay for further testing
Have you checked that they didn't modify the bundled copy?
(In reply to comment #3)
There is no reference in src/lib/3rdparty/botan that the original 1.8 source is modified so I took it for granted that the bundled copy has not been modified.
dev-libs/botan is not slotted, so I'm not sure how this is supposed to work. I need 1.10, not 1.8.
(In reply to comment #5)
It's not gonna work. qt-creator requires 1.8 and it does not build with 1.10. I am considering a useflag to control whether you want the bundled copy or not. Diego+QA, do you think a useflag for this purpose is acceptable?
Or maybe we should consider slotting libbotan...?
(In reply to comment #7)
There are lot of packages using useflags to choose between bundled and system libraries. I guess we can do the same for qt-creator for now. Whether botan can be slotted or not is not our job. We can open a bug requesting botan slotting though
How difficult would it be to support botan 1.10?
(In reply to comment #9)
Seems like the API has changed between 1.8 and 1.10 so I presume it requires source code modifications in qt-creator to match the latest API. I am not sure how easy or hard will that be.
The modified ebuild was moved to portage. I will use botan-bundled for now until I find sometime to see if the botan-1.10 API can be used in qt-creator. Thanks for reporting