# \[Haskell Cryptography Group\] Botan: The First Milestone

**URL:** <https://discourse.haskell.org/t/haskell-cryptography-group-botan-the-first-milestone/9018>\
**Category:** Announcements\
**Created:** [March 11, 2024, 1:26pm UTC](https://discourse.haskell.org/t/haskell-cryptography-group-botan-the-first-milestone/9018 "2024-03-11T13:26:44Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Bodigrim](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/bodigrim/32/1457_2.png) [@Bodigrim](https://discourse.haskell.org/u/Bodigrim)\
**Post date:** [March 11, 2024, 8:24pm UTC](https://discourse.haskell.org/t/haskell-cryptography-group-botan-the-first-milestone/9018/11 "2024-03-11T20:24:05Z")

</div>

> [@Lsmor](#):
>
> I am not familiar with foreing dependencies and maybe I am not understanding the issue, but shouldn’t users be in charge of installing the `botan3` C++ library themself? I mean, IIRC, when using (for example) haskell’s `sdl` bindings, you have to use your OS package manager to install `libsdl`, which is what I’d expected: `cabal` installs my haskell deps and just that.

Even if we restrict our considerations to Linux, at the moment no users can install Botan 3 from OS package manager and this situation will not change any time soon. We are talking about, like, 10 years from now until all not-EOL’d distros upgrade to Botan 3. So the choice is really either a user building who-knows-what who-knows-how from sources or downloading a Hackage package which does it for them in a more controlled way. I’ll chose the second option every time.

---

_[View the full topic](https://discourse.haskell.org/t/haskell-cryptography-group-botan-the-first-milestone/9018)._