Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/postgresql: needs wchar
Date: Fri, 16 Nov 2018 09:24:24 +0100	[thread overview]
Message-ID: <20181116092424.79d94e4b@windsurf> (raw)
In-Reply-To: <20181115165903.GL10271@scaer>

Hello,

On Thu, 15 Nov 2018 17:59:03 +0100, Yann E. MORIN wrote:

> I agree with Arnout here.
> 
> However, from a purely pragmatic point of view, I see that it is totally
> useless in practice, so I would not mind we drop them.
> 
> And in retrospect, I think it *is* better that we do drop them. If the
> top-level option loses that dependency, then it is 'easy' to detect it
> has become mandatory for a sub-option, because the autobuilders will
> fail.
> 
> However, if we repeat the dependency and the top-level option lses it
> and we forget to remove it, we will never realise that the sub-option
> shouldalso lose it.

That is indeed a good argument. Should we settle on the idea that we
should not uselessly replicate such dependencies ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-16  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 16:09 [Buildroot] [PATCH 1/1] package/postgresql: needs wchar Bernd Kuhls
2018-10-23 17:25 ` Adam Duskett
2018-10-23 18:04   ` Arnout Vandecappelle
2018-11-01 21:30     ` Thomas Petazzoni
2018-11-15 16:59       ` Yann E. MORIN
2018-11-16  8:24         ` Thomas Petazzoni [this message]
2018-11-20 18:35           ` Yann E. MORIN
2018-11-01 21:28 ` 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=20181116092424.79d94e4b@windsurf \
    --to=thomas.petazzoni@bootlin.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