Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out how to include dependency source code in a distribution and package it up #54

Open
theory opened this issue Sep 4, 2024 · 0 comments
Labels
design Designing the architecture, protocols, tools, and interfaces for PGXN v2 packaging

Comments

@theory
Copy link
Member

theory commented Sep 4, 2024

Experiment with adding the source for a dependency to a source code distribution such that it builds, installs, and can be packaged transparently.

Maybe try with pgsql-http. Fork it, and add the source to build the libcurl dynamic library to the project (directly, via a Git submodule, or by Makefile target) and update its Makefile to get it working with make install && make installcheck.

This pattern is probably already pretty well-supported by PGXS: should be able to something like add the library's .c file to MODULES and see it installed in the package lib dir alongside the extension module itself.

Then make sure it works for the packaging patterns developed in #52.

Done with the pattern is proven to work, ideally one example lives in the #45 registry, and the pattern has been well-documented.

@theory theory added design Designing the architecture, protocols, tools, and interfaces for PGXN v2 packaging labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Designing the architecture, protocols, tools, and interfaces for PGXN v2 packaging
Projects
Status: Backlog
Development

No branches or pull requests

1 participant