From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: GStreamer 1.0 meson build transition
Date: Mon, 28 Oct 2019 16:44:17 +0000 [thread overview]
Message-ID: <15b9c8e2-4ccc-1564-af19-fe60f049cf2e@intel.com> (raw)
In-Reply-To: <f6132fd4-18d0-aba5-96d5-c259928a113d@mailbox.org>
On 26/10/2019 11:57, Carlos Rafael Giani wrote:
> I think it would make sense to not try to get a meson based build done
> for GStreamer 1.16, and instead target it for 1.18. Minor version
> upgrades like 1.16.0 -> 1.16.1 aren't expected to bring major changes
> with them, while major upgrades like 1.16 -> 1.18 are generally known to
> potentially bring such changes. Also, there's a chance that new patches
> might make their way into 1.18 before its release.
That's fine, but there is value in doing the migration separately to the
1.16->1.18 upgrade: there should be no difference to the installed files
which makes verification easier.
Basically I've no opinion on when the meson migration is merged, as you
say it's not trivial, but please have it as a separate commit to an upgrade.
Thanks,
Ross
next prev parent reply other threads:[~2019-10-28 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 10:57 GStreamer 1.0 meson build transition Carlos Rafael Giani
2019-10-28 16:44 ` Ross Burton [this message]
2019-10-28 23:01 ` Carlos Rafael Giani
2019-10-29 12:30 ` Ross Burton
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=15b9c8e2-4ccc-1564-af19-fe60f049cf2e@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.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.