From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-devel@lists.openembedded.org
Subject: Re: [oe] RFC: meta-oe appends and overlayed recipes
Date: Tue, 12 Feb 2013 10:38:52 +0000 [thread overview]
Message-ID: <1906630.s5um26QAQj@helios> (raw)
In-Reply-To: <CAJTo0LaJNDB6XjK0M4rsS9+z7AZ6K_n0TAX8+7KH2GuAADgCZw@mail.gmail.com>
On Tuesday 12 February 2013 10:24:50 Burton, Ross wrote:
> > * tslib: OE-Core has the 1.0 release version, meta-oe has a git recipe
> > that is ahead of 1.0; the OE-Core version has two patches not in the
> > meta-oe version but that both have been merged upstream in the git
> > revision being used in the meta-oe version. There is no newer stable
> > release. What do we do here? Should we ask upstream (Chris) for a new
> > stable release?
>
> Is anyone actually using tslib these days? oe-core dropped kdrive,
> and we don't package the apparently unmaintained input driver for
> Xorg. I guess a new upstream would be good, and then move to meta-oe.
Qt Embedded as we build it is currently configured to use tslib, as is
SDL. If the alternative (evdev?) is supported they could presumably be
switched over though. I don't know how practical that is however.
> > * xserver-nodm-init: the two versions are quite distinct. Not sure I
> > understand the full history here but perhaps someone else can fill in the
> > blanks...?
>
> I don't understand the full history either yet, but this is clearly
> something that needs to be sorted.
>
> > * meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
> > As far as I can tell this just adds an /etc/busybox-syslog.default file
> > containing OPTIONS="-C64" and seems to have been added for systemd
> > support.
> > I'm not sure why this wasn't moved to meta-systemd, but I assume it needs
> > to be merged into OE-Core now that systemd support is being added
> > there... ?
> When it's understood *what* that does, then we can evaluate it for oe-core.
The following commit introduced this:
http://cgit.openembedded.org/meta-openembedded/commit/?id=c48a6a605c6d8d38cfbc5df39b3dc310bffc07c1
Otavio can you explain further?
> > * meta-oe/recipes-extended/polkit/polkit_0.104.bbappend
> > Another bbappend apparently for systemd support. Again, this should have
> > been moved to meta-systemd; do we now need to merge it into OE-Core?
>
> Yes, half of it has been merged to master already. The rest should be
> in Radu's branch, we can sort that today.
OK, great.
> > * meta-oe/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
> > Builds against external libav instead of using the builtin copy of ffmpeg,
> > apparently for better performance on ARM (and presumably that is not the
> > only benefit). It's less clear to me what should be done with this, but
> > I'd still rather it could be eliminated. OE-Core does not have
> > ffmpeg/libav; one wonders if it should or not.
>
> libav/gst-ffmpeg/gst-av (as it's called in gst1.0) has interesting
> legal issues, but I do think it should be in oe-core.
Well, we already have gst-ffmpeg in OE-Core so I can't imagine libav
would be any worse as long as it is similarly protected with
LICENSE_FLAGS.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] RFC: meta-oe appends and overlayed recipes
Date: Tue, 12 Feb 2013 10:38:52 +0000 [thread overview]
Message-ID: <1906630.s5um26QAQj@helios> (raw)
In-Reply-To: <CAJTo0LaJNDB6XjK0M4rsS9+z7AZ6K_n0TAX8+7KH2GuAADgCZw@mail.gmail.com>
On Tuesday 12 February 2013 10:24:50 Burton, Ross wrote:
> > * tslib: OE-Core has the 1.0 release version, meta-oe has a git recipe
> > that is ahead of 1.0; the OE-Core version has two patches not in the
> > meta-oe version but that both have been merged upstream in the git
> > revision being used in the meta-oe version. There is no newer stable
> > release. What do we do here? Should we ask upstream (Chris) for a new
> > stable release?
>
> Is anyone actually using tslib these days? oe-core dropped kdrive,
> and we don't package the apparently unmaintained input driver for
> Xorg. I guess a new upstream would be good, and then move to meta-oe.
Qt Embedded as we build it is currently configured to use tslib, as is
SDL. If the alternative (evdev?) is supported they could presumably be
switched over though. I don't know how practical that is however.
> > * xserver-nodm-init: the two versions are quite distinct. Not sure I
> > understand the full history here but perhaps someone else can fill in the
> > blanks...?
>
> I don't understand the full history either yet, but this is clearly
> something that needs to be sorted.
>
> > * meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
> > As far as I can tell this just adds an /etc/busybox-syslog.default file
> > containing OPTIONS="-C64" and seems to have been added for systemd
> > support.
> > I'm not sure why this wasn't moved to meta-systemd, but I assume it needs
> > to be merged into OE-Core now that systemd support is being added
> > there... ?
> When it's understood *what* that does, then we can evaluate it for oe-core.
The following commit introduced this:
http://cgit.openembedded.org/meta-openembedded/commit/?id=c48a6a605c6d8d38cfbc5df39b3dc310bffc07c1
Otavio can you explain further?
> > * meta-oe/recipes-extended/polkit/polkit_0.104.bbappend
> > Another bbappend apparently for systemd support. Again, this should have
> > been moved to meta-systemd; do we now need to merge it into OE-Core?
>
> Yes, half of it has been merged to master already. The rest should be
> in Radu's branch, we can sort that today.
OK, great.
> > * meta-oe/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bbappend
> > Builds against external libav instead of using the builtin copy of ffmpeg,
> > apparently for better performance on ARM (and presumably that is not the
> > only benefit). It's less clear to me what should be done with this, but
> > I'd still rather it could be eliminated. OE-Core does not have
> > ffmpeg/libav; one wonders if it should or not.
>
> libav/gst-ffmpeg/gst-av (as it's called in gst1.0) has interesting
> legal issues, but I do think it should be in oe-core.
Well, we already have gst-ffmpeg in OE-Core so I can't imagine libav
would be any worse as long as it is similarly protected with
LICENSE_FLAGS.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-02-12 10:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 17:09 RFC: meta-oe appends and overlayed recipes Paul Eggleton
2013-02-11 17:50 ` Otavio Salvador
2013-02-11 17:50 ` [OE-core] " Otavio Salvador
2013-02-12 8:38 ` Anders Darander
2013-02-12 8:38 ` [OE-core] " Anders Darander
2013-02-11 22:35 ` Richard Purdie
2013-02-11 22:35 ` [OE-core] " Richard Purdie
2013-02-12 9:24 ` Paul Eggleton
2013-02-12 9:24 ` [OE-core] " Paul Eggleton
2013-02-12 13:10 ` Richard Purdie
2013-02-12 13:10 ` [OE-core] " Richard Purdie
2013-02-12 13:38 ` Paul Eggleton
2013-02-12 13:38 ` [OE-core] " Paul Eggleton
2013-02-12 10:24 ` [oe] " Burton, Ross
2013-02-12 10:24 ` Burton, Ross
2013-02-12 10:38 ` Paul Eggleton [this message]
2013-02-12 10:38 ` [OE-core] " Paul Eggleton
2013-02-12 16:43 ` [oe] " Otavio Salvador
2013-02-12 16:43 ` [OE-core] " Otavio Salvador
2013-02-12 20:51 ` [oe] " Burton, Ross
2013-02-12 20:51 ` [OE-core] " Burton, Ross
2013-02-12 21:22 ` [oe] " Martin Jansa
2013-02-12 21:22 ` [OE-core] " Martin Jansa
2013-02-12 21:36 ` [oe] " Burton, Ross
2013-02-12 21:36 ` [OE-core] " Burton, Ross
2013-02-12 21:40 ` [oe] " Otavio Salvador
2013-02-12 21:40 ` [OE-core] " Otavio Salvador
2013-02-12 21:53 ` [oe] " Eric Bénard
2013-02-12 21:53 ` [OE-core] " Eric Bénard
2013-02-12 22:02 ` [oe] " Burton, Ross
2013-02-12 22:02 ` [OE-core] " Burton, Ross
2013-02-12 15:50 ` [oe] " Ross Burton
2013-02-12 15:50 ` Ross Burton
2013-02-12 16:44 ` [oe] " Otavio Salvador
2013-02-12 16:44 ` [OE-core] " Otavio Salvador
2013-02-12 16:53 ` [oe] " Paul Eggleton
2013-02-12 16:53 ` [OE-core] " Paul Eggleton
2013-02-12 19:19 ` Martin Jansa
2013-02-12 19:19 ` [OE-core] " Martin Jansa
2013-02-12 19:31 ` [oe] " Otavio Salvador
2013-02-12 19:31 ` [OE-core] " Otavio Salvador
2013-02-12 19:32 ` Paul Eggleton
2013-02-12 19:32 ` [OE-core] " Paul Eggleton
2013-02-12 19:51 ` Martin Jansa
2013-02-12 19:51 ` [OE-core] " Martin Jansa
2013-02-12 20:40 ` Marcin Juszkiewicz
2013-02-12 19:32 ` [oe] " Chris Larson
2013-02-12 19:32 ` [OE-core] " Chris Larson
2013-02-12 19:59 ` [oe] " Mark Hatle
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=1906630.s5um26QAQj@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.