Create a package KNITRO_jll.jl ?

[amontoison]

@odow
I am wondering if we should not try to do a KNITRO_jll.jl like you did with Xpress_jll.jl and GUROBI_jll.jl.
What do you think?

[odow]

This requires permission from Artelys for the binaries to be publicly available (e.g., pip install knitro), which I don't believe is the case?

[amontoison]

I quickly discuss about that with an employee of Artelys during ISMP.
I will contact them next week.

In the worst case they can do like HSL and have a dummy version of the JLL.
It will allow Artelys to not provide the official KNITRO_jll.jl with precompiled binaries to everyone if it's the issue.

[mgabay]

Hi all,

I would like this.
We'll discuss about it and get back to you in September.

So far we've avoided it but this is currently under consideration, although there are a few things we need to figure out.

@Bougron : tbd after our vacations

[odow]

Thanks @mgabay.

The precedent for this is:

• https://github.com/jump-dev/Gurobi_jll.jl
• https://github.com/jump-dev/Xpress_jll.jl

They both pull from the official anaconda sources, e.g., https://anaconda.org/Gurobi/gurobi, so something similar would be our ideal. I guess my suggestion is "don't treat this as a Julia issue. Treat it as a Python packaging problem, and we can re-use that solution."

[amontoison]

@mgabay
Any update from Artelys?
I'm available for a meeting if that could help facilitate the discussion.

[mgabay]

Hi @amontoison ,

We plan to do it for Python so that you can then setup something similar to other solvers.
However, we have yet to figure out a few details and put it in the roadmap.
This is probably going to be for Q1 2025 but it is not scheduled yet.