Can you elaborate on (why, perhaps) "Actually move to OpenSSL to remove Botan dependency"? I changed "botan-2" -> "botan-3" about 3 days ago (in my home repo) and the unresolved was resolved and u++ doesn't seem to behave any differently. Maybe Botan (specifically) isn't/wasn't necessary at any point and swapping in libcrypto is 1:1, I think it only came up at some point around this timeframe: https://github.com/jstkdng/ueberzugpp/issues/17

EDIT: maybe 'pkgconfig(botan-3)' pulls in [what] 'pkgconfig(libcrypto)' [provides] - coincidentally - and you're saying since botan isn't directly needed, just use pkgconfig(libcrypto) instead?

Andreas Stieger (AndreasStieger) - about 1 month ago

author

I was referring to this previous changelog entry:

  * use openssl instead of botan

If you are in a position to consume Botan 3 on TW and it works for you please go ahead. We dropped Botan 2 on TW and are not looking to maintain a transitional package.

---

Scott Bradnick (sbradnick) - about 1 month ago

target maintainer

Ahh, good eye 😉 - that's from the developer's commits, so it does look like they transitioned away from botan quite a while ago and it was just a bit of luck that openssl was pulled in like that by botan. I'll swap botan-3->libcrypto over and push the latest commits for u++ today.

Thanks for pointing it out 👍.

---

Andreas Stieger (AndreasStieger) - about 1 month ago

author

thanks for checking