Replies: 4 comments 1 reply
-
The extra exported libraries are interfaces for external applications to configure Dune. As they are layers over some of Dune's internals, it doesn't make sense to distribute them without Dune itself (or to distribute Dune without them -- they're linked into the Dune binary anyway). As far as I know, we don't maintain the Arch Linux package (at least, none of the names of the maintainers of that package are familiar to me), so you'll have to ask them why it's built the way it is. EDIT: Confirmed, we don't maintain that package. The two supported ways of installing Dune are from source as detailed in the README or via opam. |
Beta Was this translation helpful? Give feedback.
-
When dune is built according to the above instructions ( There is a circular dependency problem: csexp depends on dune, and dune with additional libraries depends on csexp. |
Beta Was this translation helpful? Give feedback.
-
You are conflating "building" with "packaging". By specifying
The |
Beta Was this translation helpful? Give feedback.
-
These build commands fail:
Somehow it fails to pick up the vendored |
Beta Was this translation helpful? Give feedback.
-
README says:
But for many projects dune needs to be built with other packages.
Arch linux builds like this:
Is this correct? Is the list of packages complete?
See the Arch package here: https://github.com/archlinux/svntogit-community/blob/packages/dune/trunk/PKGBUILD
Why are these additional packages bundled with dune? Shouldn't they be separate packages?
Beta Was this translation helpful? Give feedback.
All reactions