From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add support for Meson build
Date: Wed, 11 Oct 2017 23:21:47 +0200 [thread overview]
Message-ID: <20171011232147.4206a377@windsurf.lan> (raw)
In-Reply-To: <8186cfc2-f587-8d35-2560-2f2f314a186d@mind.be>
Hello,
On Wed, 11 Oct 2017 22:38:39 +0200, Arnout Vandecappelle wrote:
> Yes, our original idea was that there should be a few packages using meson
> before we add an infra for it. But since there are quite a few packages that
> will use the meson infra, and since it seems pretty straightforward, it can
> indeed be done right away (at least according to me, Thomas may have a different
> opinion).
Yes, I believe it's fine to have a Meson package infrastructure right
away. There is a clear trend towards using Meson, so I'm fine with
merging a package infrastructure for it.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-11 21:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 9:45 [Buildroot] [PATCH 0/3] Add support for Meson build Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH v2 1/3] meson: new package Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH v2 2/3] docs/manual: document meson-based packages Jörg Krause
2017-07-27 9:45 ` [Buildroot] [PATCH 3/3] libmpdclient: bump to version 2.13 Jörg Krause
2017-07-27 10:11 ` [Buildroot] [PATCH 0/3] Add support for Meson build Vicente Olivert Riera
2017-07-27 10:13 ` Jörg Krause
2017-07-27 10:19 ` Vicente Olivert Riera
2017-07-27 14:50 ` Thomas Petazzoni
2017-10-06 22:34 ` Andrey Yurovsky
2017-10-06 22:39 ` Andrey Yurovsky
2017-10-07 11:58 ` Thomas Petazzoni
2017-10-07 13:06 ` Romain Naour
2017-10-11 3:51 ` Andrey Yurovsky
2017-10-11 6:55 ` Eric Le Bihan
2017-10-12 6:42 ` Jörg Krause
2017-10-13 11:49 ` Adam Duskett
2017-10-11 20:38 ` Arnout Vandecappelle
2017-10-11 21:21 ` Thomas Petazzoni [this message]
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=20171011232147.4206a377@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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