From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gst1-plugins-imx: add package
Date: Sat, 08 Nov 2014 23:01:21 +0100 [thread overview]
Message-ID: <8761eps66m.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CADCpmyOMtq1vf9TtZJ-=JaRR67qiSQoX5k5CZ7T0jqYav2GWeA@mail.gmail.com> (Gary Bisson's message of "Mon, 3 Nov 2014 14:47:48 -0800")
>>>>> "Gary" == Gary Bisson <bisson.gary@gmail.com> writes:
Hi,
> ?I'm sorry to return to the naming issue, but shouldn't the package be
> called
> gst1-imx instead of gst1-plugins-imx? We don't use 'plugins' in any other
> gst
> package (except the official plugin bundles), and upstream also doesn't
> have
> 'plugins' in the name.
> ?
> I see your point and really changing the name doesn't bother me, we just need
> to agree on something. How do we organize a vote? irc? ;-) So far Peter K
> suggested "gstreamer1-imx", Arnout "gst1-imx" and mine "gst1-plugins-imx". As a
> reminder the git repo name is "gstreamer-imx" and the Yocto recipe is
> "gstreamer1.0-plugins-imx". Since the first version of this patch have been
> integrated two plugins:gst1-libav and gst1-validate which tends towards a gst1-
> <name> convention.
Yes, so lets go with gst1-imx.
>> +? ? ?depends on BR2_arm # Only relevant for i.MX
>> +? ? ?depends on BR2_TOOLCHAIN_USES_GLIBC # gpu-viv-bin-mx6q
>> +? ? ?depends on BR2_PACKAGE_GPU_VIV_BIN_MX6Q
> ?This should be a select.
> We unfortunately discussed that before and Yann came to the conclusion it
> wasn't possible for now [1]. Otherwise this requires reworking all the iMX
> platforms selections in freescale-imx packages.
Ahh yes, so lets leave it as depends on (for both).
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-11-08 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 2:32 [Buildroot] [PATCH v2] gst1-plugins-imx: add package Gary Bisson
2014-11-02 22:13 ` Luca Ceresoli
2014-11-03 21:33 ` Arnout Vandecappelle
2014-11-03 21:51 ` Arnout Vandecappelle
2014-11-03 22:47 ` Gary Bisson
2014-11-08 22:01 ` Peter Korsgaard [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=8761eps66m.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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