From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] postgresql: new package
Date: Fri, 04 Apr 2014 08:04:16 +0200 [thread overview]
Message-ID: <533E4B60.8090804@mind.be> (raw)
In-Reply-To: <20140403223952.37034a1a@skate>
On 03/04/14 22:39, Thomas Petazzoni wrote:
> Dear Peter Seiderer,
>
> On Mon, 31 Mar 2014 08:59:29 +0200, Peter Seiderer wrote:
>
[snip[
>> +if [ ! -f /srv/pgsql/data/PG_VERSION ]; then
>
> I thought we changed to /var/lib/pgsql ?
>
> Maybe you should create a variable that contains /var/lib/pgsql to
> avoid this duplication.
I'm opposed to such variables, I don't see how they give an advantage:
- they make the code less readable (you have to look up what
POSTGRESQL_DATABASE_PATH expands to);
- they make the code longer (extra line for the assignment, and
POSTGRESQL_DATABASE_PATH is not significantly shorter than /var/lib/pgsql);
- changing the path is quite trivial as long as it stays in the same file
(I admit that I assume that you vi-users know how to escape a /).
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-04-04 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 6:59 [Buildroot] [PATCH] postgresql: new package Peter Seiderer
2014-04-03 20:39 ` Thomas Petazzoni
2014-04-04 6:04 ` Arnout Vandecappelle [this message]
2014-04-04 19:15 ` Peter Seiderer
2014-04-03 21:55 ` Jerzy Grzegorek
2014-04-04 19:18 ` Peter Seiderer
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 20:56 Peter Seiderer
2014-03-08 21:59 Peter Seiderer
2014-03-16 12:15 ` Marco Trapanese
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=533E4B60.8090804@mind.be \
--to=arnout@mind.be \
--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