How to best work around needing external dependencies for source installs? #5814
Unanswered
matthewfeickert
asked this question in
Q&A
Replies: 2 comments 4 replies
-
|
It should be possible to add support for using |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Have you tried with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
With
pixi addwe have the ability to add Python packages to the workspace from source bywhich is very useful. However, we are not able to use software defined in our environment to build the installed packages and depend on external software. For example, if
pixi installis run on the following Pixi manifestin an environment without an externally defined Git, it will fail.
We instead need to install Git first from an external process for the build to use
While the obvious answer here is "use built software distributions", it is still interesting to note that a source distribution of software even if pinned to the rev is not actually fully reproducible by the Pixi workspace itself.
What are the recommended approaches to working around this in a reproducible way? I suppose one of them would be "ensure that your source dependencies have
pixi-buildsupport"?Beta Was this translation helpful? Give feedback.
All reactions