You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conda-libmamba-solver only relies on the solver part of libmamba. It doesn't use any of the extraction routines, or the networking stack. Would it be possible to build libmamba in different chunks? Something like:
libmamba-archive.so
libmamba-network.so
libmamba-solver.so
libmamba-common.so
... plus the corresponding Python counterparts if needed.
with libarchive and libcurl bringing most of the leaves. If I could have conda-libmamba-solver depend on simply libmambapy-solver then all those libraries won't be needed in the conda dependency tree.
conda-libmamba-solver
only relies on the solver part oflibmamba
. It doesn't use any of the extraction routines, or the networking stack. Would it be possible to build libmamba in different chunks? Something like:libmamba-archive.so
libmamba-network.so
libmamba-solver.so
libmamba-common.so
... plus the corresponding Python counterparts if needed.
The dependency tree is currently:
with
libarchive
andlibcurl
bringing most of the leaves. If I could haveconda-libmamba-solver
depend on simplylibmambapy-solver
then all those libraries won't be needed in theconda
dependency tree.Another side benefit is that we would diminish the ABI surface for errors like this conda-forge/libarchive-feedstock#69.
I know this is probably a big ask, and certainly not urgent, but I'll leave it here for reference.
The text was updated successfully, but these errors were encountered: