All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Ezequiel Garcia <ezequiel@collabora.com>,
	linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
	Sean Young <sean@mess.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [RFC PATCH v4l-utils 1/1] Introduce support for meson building
Date: Thu, 26 Mar 2020 20:00:36 -0400	[thread overview]
Message-ID: <1df4b3c75ebef8001b2d47a8dbe1d688b4df0968.camel@ndufresne.ca> (raw)
In-Reply-To: <20200325102654.GE4760@pendragon.ideasonboard.com>

Le mercredi 25 mars 2020 à 12:26 +0200, Laurent Pinchart a écrit :
> > Custom reporting is no longer recommended, meson have a option driven
> > report (summary). The plus side is that it will be printed at the end
> > properly even if this project is used as subproject.
> 
> I didn't know about that, it's nice. The option has been added to meson
> 0.53 though, which may be a tad too recent ?

Indeed, but be careful with such an argument, since someone could come back and
say meson is too early, it's not over 10 years old yet. I think best is too look
at how often distro updates this library. If they only update when the entire
distro is updated, my recommendation is to use the version that best suite your
work. If they tend to backport on stable distro, then maybe it's best to be
conservative.

In GStreamer we do both, we stick with older meson in stable release (1.16)
unless there is a bug in meson that caused a bad build. And use the most recent
version in development, so that next when distro moves to a new stable, they
have to update meson at the same time, obviously for the benifit of their users.
(Also because a some upcoming meson feature are written by GStreamer developers,just to be honnest). 

Nicolas


  reply	other threads:[~2020-03-27  0:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 20:54 [RFC PATCH v4l-utils 0/1] Introduce the meson build system Ezequiel Garcia
2020-03-15 20:54 ` [RFC PATCH v4l-utils 1/1] Introduce support for meson building Ezequiel Garcia
2020-03-16  9:43   ` Laurent Pinchart
2020-03-16 18:44     ` Ezequiel Garcia
2020-03-16 18:07   ` Nicolas Dufresne
2020-03-21 13:11     ` Ezequiel Garcia
2020-03-25 10:26     ` Laurent Pinchart
2020-03-27  0:00       ` Nicolas Dufresne [this message]
2020-03-16  8:53 ` [RFC PATCH v4l-utils 0/1] Introduce the meson build system Laurent Pinchart
2020-03-16  9:25   ` Sean Young
2020-03-16  9:17 ` Hans Verkuil
2020-03-16 16:29   ` Ezequiel Garcia
2020-03-16 17:53     ` Nicolas Dufresne
2020-03-16 17:30 ` Mauro Carvalho Chehab
2020-03-16 17:32   ` Laurent Pinchart
2020-03-16 17:47   ` Nicolas Dufresne

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=1df4b3c75ebef8001b2d47a8dbe1d688b4df0968.camel@ndufresne.ca \
    --to=nicolas@ndufresne.ca \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=sean@mess.org \
    /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.