Package manager discussion #177
Replies: 7 comments 25 replies
-
I believe that keeping things to
The alternatives you posted are all very good, but let's keep them on the shelf until sometime when it's ready to consider this issue. |
Beta Was this translation helpful? Give feedback.
-
This would be an unmaintainable mess. The point of a package manager is that updating dependencies is easy.
The telemetry can be disabled easily, so I don't think this is really a problem.
The package list is really small.
Limitations are significant. There is MSYS2, but that only helps on Windows, not macOS. AFAIK vcpkg seems to be the only viable alternative to Conan. I would be happy to be wrong about that. |
Beta Was this translation helpful? Give feedback.
-
Is there any issue with conan that is solved by the other ones? |
Beta Was this translation helpful? Give feedback.
-
conan is used upstream, IMO it makes perfect sense to keep it as long as tenacity is still running in sync with it. |
Beta Was this translation helpful? Give feedback.
-
Conan doesn't support musl libc natively, which means Alpine Linux users might encounter problems building from source. The Alpine maintainer for Audacity stated they'll only package the project if we support musl upstream, so we can't use a package manager that doesn't. |
Beta Was this translation helpful? Give feedback.
-
If Conan doesn't support musl and other package managers don't support this or that dependency, is using submodules for unsupported dependencies so much of a problem? |
Beta Was this translation helpful? Give feedback.
-
@falkTX you have mentioned cross compiling from Linux to Windows and macOS. What options are available for package managers for cross compiled dependencies? I think Conan and vcpkg can both be used for this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
tenacity currently uses the conan package manager to manage some of the C++ dependencies
The question is, should tenacity keep using Conan to match the upstream builds or should it be switched to a different one? (Or completely none?)
Here is a list of possible alternatives:
Beta Was this translation helpful? Give feedback.
All reactions