# Recommand \`curl | bash\` as default installation is not ideal?

**URL:** <https://discourse.julialang.org/t/recommand-curl-bash-as-default-installation-is-not-ideal/121820>\
**Category:** General Usage\
**Created:** [October 27, 2024, 11:34am UTC](https://discourse.julialang.org/t/recommand-curl-bash-as-default-installation-is-not-ideal/121820 "2024-10-27T11:34:28Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![asinghvi17](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/asinghvi17/32/8272_2.png) [@asinghvi17](https://discourse.julialang.org/u/asinghvi17)\
**Post date:** [October 29, 2024, 2:37am UTC](https://discourse.julialang.org/t/recommand-curl-bash-as-default-installation-is-not-ideal/121820/8 "2024-10-29T02:37:11Z")

</div>

Ah, maybe it’s purely a package problem then. But if you load the JLL OpenSSL before the Python one in a session with PythonCall, and the two versions are not the same, Python will not be able to successfully call into OpenSSL. (There’s a fix for this in CondaPkg.jl for this exact reason).

I guess the problem is getting Pkg info to Conda, from the Conda end…(since the Julia/Pkg end is solved via CondaPkg!)

A bigger problem is coordinating JLL versions between different packages, since Julia JLLs often don’t share the upstream project’s exact version number (take Proj\_jll as an example, which multiplies all version numbers by 100).

---

_[View the full topic](https://discourse.julialang.org/t/recommand-curl-bash-as-default-installation-is-not-ideal/121820)._