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

Improve Installation Message on Ubuntu #23

Open
JulianBirch opened this issue Sep 22, 2014 · 4 comments
Open

Improve Installation Message on Ubuntu #23

JulianBirch opened this issue Sep 22, 2014 · 4 comments

Comments

@JulianBirch
Copy link

When I install something that uses postgresql-libpq and get the following message:

You need to install postgresql-server-dev-X.Y for building a
server-side extension or libpq-dev for building a client-side application.

It'd be nice to include some text pointing someone at apt-get to avoid confusion between installing OS packages and cabal packages.

@lpsmith
Copy link
Owner

lpsmith commented Sep 22, 2014

Honestly, I'm not even sure where that message is coming from, it's not coming from postgresql-libpq or cabal. It has to be some trick Ubuntu is pulling when GHC/Cabal's build process is running CPP and trying to include the non-existent libpq headers.

So, I don't think it's really all that fixable, other than doing a apt-get install libpq-dev or the like. Though there should be some installation instructions included in the .cabal Description field.

@JulianBirch
Copy link
Author

Oh well :(

@lpsmith
Copy link
Owner

lpsmith commented Sep 24, 2014

Well, I'll definitely try to work on the installation instructions soon, which should help.

Since Hackage is a bit funky in the way that the description field is rendered, I'm thinking of just having the instructions as the README.md on github with a link in the description field. Which is not as good, but still a big step in the right direction...

@lpsmith
Copy link
Owner

lpsmith commented Sep 24, 2014

Alternatively, if you track down how Ubuntu is generating that message, you might suggest this sort of improvement there...

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

2 participants