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

Add configuration option for a list of extensions to compile #5

Open
rdunklau opened this issue Mar 13, 2018 · 4 comments
Open

Add configuration option for a list of extensions to compile #5

rdunklau opened this issue Mar 13, 2018 · 4 comments

Comments

@rdunklau
Copy link

Currently, the configuration file supports various features. It would be great if we could similarly give a list of extensions we would like to compile and install in the current instance.

Those extensions could either:

  • be installed via the pgxnclient (simple, but add another dependency)
  • be built from an extension directory (to be specified in the config file), where the name of the extension should match the source folder for this extension (more grassroots, but doesn't need any dependency).
@marco44
Copy link
Collaborator

marco44 commented Mar 13, 2018

Mmm, maybe we should only do that for extensions conforming to the PGXS way of doing this ? This would be trivial...

@rjuju
Copy link
Owner

rjuju commented Mar 16, 2018

+1 for PGXN.

@marco44
Copy link
Collaborator

marco44 commented Mar 17, 2018

I wrote PGXS :)

@rjuju
Copy link
Owner

rjuju commented Mar 17, 2018

Indeed :) I meant PGXN client, simplest solution but with a dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants