From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/postgresql: needs wchar
Date: Tue, 20 Nov 2018 19:35:09 +0100 [thread overview]
Message-ID: <20181120183509.GD2601@scaer> (raw)
In-Reply-To: <20181116092424.79d94e4b@windsurf>
Thomas, All,
On 2018-11-16 09:24 +0100, Thomas Petazzoni spake thusly:
> On Thu, 15 Nov 2018 17:59:03 +0100, Yann E. MORIN wrote:
> > 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 ?
Yes, let's not replicate them.
And accept patches that removes them.
And accept a patch that updates the manual accordnigly, of course! ;-)
(I'll see what I can do...)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-20 18:35 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
2018-11-20 18:35 ` Yann E. MORIN [this message]
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=20181120183509.GD2601@scaer \
--to=yann.morin.1998@free.fr \
--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