From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/7] gstreamer1: Add gstreamer version 1.0.7 package
Date: Sun, 12 May 2013 19:16:49 +0200 [thread overview]
Message-ID: <518FCE81.3070002@mind.be> (raw)
In-Reply-To: <20130512112313.12a809e3@skate>
On 12/05/13 11:23, Thomas Petazzoni wrote:
> On Sat, 11 May 2013 23:31:12 +0200, Peter Korsgaard wrote:
>
>> > Arnout> We have a tendency to make a copy of a package when there is a major
>> > Arnout> version change, cfr. python3 and qt5. However, in this case, I don't
>> > Arnout> think it's a good idea. At this time, many (most?) gstreamer
>> > Arnout> downstreams have already moved to 1.x. Also, no more patches will be
>> > Arnout> made the the 0.10 series (though distro's may still make patches). So
>> > Arnout> we can expect the old gstreamer stuff to die out relatively
>> > Arnout> quickly. But if we call the new thing gstreamer1 now, we're
>> > Arnout> essentially stuck with that name for all eternity.
>> >
>> >I'm not so sure. If you look at the other recent major version upgrades
>> >(python/qt/gtk), it seems to me like people aren't jumping on the new
>> >version right away. I had several people asking me if qt4 would still be
>> >available once qt5 got added.
> I agree. I recently had a customer using Buildroot, with a fairly
> important stack of custom/proprietary software written on top of
> gstreamer 0.10. Having the possibility to continue to use gstreamer
> 0.10 is very important to allow such users to migrate to newer
> Buildroot versions. The migration to gstreamer 1.x will not happen
> overnight for such users who have a large body of software written
> against gstreamer 0.10.
>
> Similarly for Qt4 vs. Qt5, as Peter mentioned.
Fair enough. I guess Peter's right, having the 1 in the name doesn't hurt.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-05-12 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 4:02 [Buildroot] Gstreamer 1.X Patches Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 1/7] gstreamer1: Add gstreamer version 1.0.7 package Spenser Gilliland
2013-05-10 23:38 ` Arnout Vandecappelle
2013-05-11 21:31 ` Peter Korsgaard
2013-05-12 9:23 ` Thomas Petazzoni
2013-05-12 11:13 ` Peter Korsgaard
2013-05-12 11:36 ` Thomas Petazzoni
2013-05-12 17:16 ` Arnout Vandecappelle [this message]
2013-05-13 17:43 ` Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 2/7] gst1-plugins-base: add gstreamer1 base plugins Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 3/7] gst1-plugins-good: add gstreamer1 good plugins Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 4/7] gst1-plugins-bad: add gstreamer1 bad plugins Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 5/7] gst1-plugins-ugly: add gstreamer1 ugly plugins Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 6/7] libvpx: new package libvpx Spenser Gilliland
2013-05-10 4:02 ` [Buildroot] [PATCH v3 7/7] gst1-plugins-good: add libvpx support Spenser Gilliland
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=518FCE81.3070002@mind.be \
--to=arnout@mind.be \
--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