From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] docs/manual: document meson-based packages
Date: Mon, 18 Jul 2016 11:13:21 +0200 [thread overview]
Message-ID: <20160718111321.40fc5ee8@free-electrons.com> (raw)
In-Reply-To: <20160717163724.GN3614@free.fr>
Hello,
On Sun, 17 Jul 2016 18:37:24 +0200, Yann E. MORIN wrote:
> > +Buildroot does not (yet) provide a dedicated package infrastructure for
> > +meson-based packages.
>
> So why not provide one? A new infra is not trivial to write, indeed, but
> given your example, the meson-package does not look like it is a complex
> one to write (see below).
>
> However, considering that we have no package that use meson yet, and
> that you do not plan on sending one shortly, what's the point in having
> either an infra or even this documentation?
I prefer to have an infrastructure once we have a few packages that
actually use meson. Until it is the case, I prefer to not have a
package infrastructure for this, especially since using generic-package
for Meson packages remains pretty simple, according to Eric's
documentation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-18 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 13:49 [Buildroot] [PATCH 0/2] Meson: new build system Eric Le Bihan
2016-07-09 13:49 ` [Buildroot] [PATCH 1/2] meson: new package Eric Le Bihan
2016-07-17 16:11 ` Yann E. MORIN
2016-07-18 8:14 ` Eric Le Bihan
2016-07-17 16:23 ` Yann E. MORIN
2016-07-18 8:57 ` Eric Le Bihan
2016-10-16 13:19 ` Arnout Vandecappelle
2016-07-09 13:49 ` [Buildroot] [PATCH 2/2] docs/manual: document meson-based packages Eric Le Bihan
2016-07-17 16:37 ` Yann E. MORIN
2016-07-18 9:13 ` 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=20160718111321.40fc5ee8@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.