From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] postgresql: remove devfiles from target
Date: Sun, 17 Aug 2014 21:57:54 +0200 [thread overview]
Message-ID: <53F10942.4070801@je-eigen-domein.nl> (raw)
In-Reply-To: <20140817211717.5ddb2a1b@free-electrons.com>
On 08/17/2014 09:17 PM, Thomas Petazzoni wrote:
> On Wed, 13 Aug 2014 15:57:10 +0200, Floris Bos wrote:
>> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
>> ---
>> package/postgresql/postgresql.mk | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/package/postgresql/postgresql.mk b/package/postgresql/postgresql.mk
>> index dd2e678..19f9163 100644
>> --- a/package/postgresql/postgresql.mk
>> +++ b/package/postgresql/postgresql.mk
>> @@ -52,6 +52,7 @@ endef
>>
>> define POSTGRESQL_INSTALL_TARGET_FIXUP
>> $(INSTALL) -dm 0700 $(TARGET_DIR)/var/lib/pgsql
>> + $(RM) -rf $(TARGET_DIR)/usr/lib/postgresql/pgxs
>> endef
>>
>> POSTGRESQL_POST_INSTALL_TARGET_HOOKS += POSTGRESQL_INSTALL_TARGET_FIXUP
> I've applied the patch, thanks. However, I'm not sure to understand
> why you're not removing 'pg_config' from the target.
Thomas DS mentioned that having "POSTGRESQL_CONFIG_SCRIPTS = pg_config"
also causes automatic removal from the target
And have that in the first patch of the patch series that adds the fake
pg_config file.
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2014-08-17 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 13:57 [Buildroot] [PATCH v2 1/3] postgresql: add replacement pg_config Floris Bos
2014-08-13 13:57 ` [Buildroot] [PATCH v2 2/3] postgresql: remove devfiles from target Floris Bos
2014-08-17 19:17 ` Thomas Petazzoni
2014-08-17 19:57 ` Floris Bos [this message]
2014-08-13 13:57 ` [Buildroot] [PATCH v2 3/3] php: add pdo_pgsql extension Floris Bos
2014-08-17 19:21 ` Thomas Petazzoni
2014-08-17 19:20 ` [Buildroot] [PATCH v2 1/3] postgresql: add replacement pg_config Thomas Petazzoni
2014-08-17 19:22 ` Thomas Petazzoni
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=53F10942.4070801@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--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