Open ohhmm opened 3 weeks ago
cc @JavierMatosD @BillyONeal
Note that export
produces a single package containing an entire installed tree, so it still wouldn't allow "seamless tight choices between system and produced dependencies". Moreover, most dependencies in the world aren't ABI compatible, so trying to replace some of them with system ones will explode at runtime.
That is right @BillyONeal, and this is why it is unusable for APT-based distros in space-efficient manner. This is why I suggest to generate DEB/RPM per each vcpkg dependency semi-automatically.
Is your feature request related to a problem? Please describe.
Vcpkg deep extensive dependencies scares somehow developers from binding 51 dependency to bind boost::program_options.
Proposed solution
Adding equivalent apt repo (for Ubuntu) would allow seamless tight choices between system and produced dependencies. Vcpkg seem to have everything ready to produce a package repository. Please, consider adding apt repository generator vcpkg new feature.
Describe alternatives you've considered
Tried convincing that 51 dependencies is not a problem for vcpkg.
Additional context
vcpkg export apt <path> [--options...]