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: Thu, 1 Nov 2018 22:30:46 +0100	[thread overview]
Message-ID: <20181101223046.72222a3c@windsurf> (raw)
In-Reply-To: <643ca3d2-1825-4707-5fbb-0817229188f9@mind.be>

Hello,

On Tue, 23 Oct 2018 19:04:26 +0100, Arnout Vandecappelle wrote:

>  It is not strictly needed, but it is still useful to have it because:

True. In this case:

 - Bernd did not propagate the dependency to p?p, qt and qt5base, which
   all three are also directly selecting BR2_PACKAGE_POSTGRESQL

 - A number of places where BR2_PACKAGE_POSTGRESQL is selected do not
   have the !BR2_STATIC_LIBS dependency.

I am really wondering what to do with those "useless" dependencies in
general. On one hand, I agree with you that semantically, it is better
to have them. On the other hand:

 - It's an additional maintenance burden.

 - It's never tested by the autobuilders, because such "useless"
   dependencies are well, useless, because they are hidden by another
   higher-level dependency. Because they are not tested, they are often
   wrong and not maintained.

Due to this, whether we propagate them or not is completely random
currently through the Buildroot tree, and I'm not sure it's a very nice
situation.

Best regards,

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

  reply	other threads:[~2018-11-01 21:30 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 [this message]
2018-11-15 16:59       ` Yann E. MORIN
2018-11-16  8:24         ` Thomas Petazzoni
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=20181101223046.72222a3c@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