From: Ben Boeckel <mathstuf@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] Add postgres server/client options
Date: Sun, 18 Oct 2015 10:51:59 -0400 [thread overview]
Message-ID: <1445179920-2413-1-git-send-email-mathstuf@gmail.com> (raw)
Currently it is possible to turn on postgres and have both client and server
off. Making it an either/or seemed like too much of a break for those wanting
both, but I'm unsure of how to enforce at-least-one-of a set not available
until the postgres package is enabled.
Both options default to 'y' for backwards compat.
The procedure is as documented here (at the end):
http://www.postgresql.org/docs/9.4/static/install-procedure.html
but I used FreeBSD's directory listing which also excludes the other
server-only bits and allows server-without-client mode as well.
If the simpler procedure on the webpage is wanted, I'm fine with that as well.
Tested in client, server, and client+server mode locally on x86_64.
Thanks,
--Ben
Ben Boeckel (1):
postgresql: add an option to build the server
package/bandwidthd/Config.in | 1 +
package/collectd/Config.in | 1 +
package/cppdb/Config.in | 2 +-
package/php/Config.ext | 1 +
package/postgresql/Config.in | 16 ++++++++++++++
package/postgresql/postgresql.mk | 48 ++++++++++++++++++++++++++++++++++++++++
package/qt/Config.sql.in | 1 +
package/qt5/qt5base/Config.in | 1 +
8 files changed, 70 insertions(+), 1 deletion(-)
--
2.6.1
next reply other threads:[~2015-10-18 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 14:51 Ben Boeckel [this message]
2015-10-18 14:52 ` [Buildroot] [PATCH 1/1] postgresql: add an option to build the server Ben Boeckel
2015-10-18 16:19 ` Thomas Petazzoni
2015-10-18 21:46 ` Ben Boeckel
2015-10-18 16:04 ` [Buildroot] [PATCH 0/1] Add postgres server/client options Thomas Petazzoni
2015-10-23 4:43 ` [Buildroot] [PATCH v2 1/1] postgresql: add an option to build the server Ben Boeckel
2015-10-31 17:58 ` Ben Boeckel
2015-11-19 1:52 ` Ben Boeckel
2015-12-13 22:37 ` Thomas Petazzoni
2015-12-14 0:08 ` Arnout Vandecappelle
2015-12-14 21:55 ` Yann E. MORIN
2016-04-19 21:22 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1445179920-2413-1-git-send-email-mathstuf@gmail.com \
--to=mathstuf@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox