From: Philip Balister <philip@balister.org>
To: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto usability questions
Date: Thu, 17 Nov 2011 09:25:35 -0500 [thread overview]
Message-ID: <4EC5195F.5060302@balister.org> (raw)
In-Reply-To: <4EC506D2.3080901@ts.fujitsu.com>
On 11/17/2011 08:06 AM, Rainer Koenig wrote:
> Hi Jeff,
>
> On 16.11.2011 23:07, Jeff Osier-Mixon wrote:
>
>>> Mark & everyone else listening:
> I include myself in the "everyone" group and answer. ;-)
>
> Another problem seems, that you always need to work on the *latest*
> version of the recipe-trees since they are depending from the
> availability of the upstream sources. If sources change, disappear or
> move then the recipe needs to be adapted. Now I know that, but in the
> beginning it was just frustrating to get error messages any time I tried
> to build something.
>
This is the number one issue with the openembedded-core/meta-oe
combination. There is no system in place to publish a list of known good
revisions for people who are trying to get real work done. Currently,
I'm stuck because guile won't build. (I also see the samba issue, but
dropped it from gvfs). I've been around a long time, and there are still
some build issues that stump me. Personally, I need this stuff to work
so I can get stuff done for paying customers. I don't care if recipes
are perfect, or we have the latest version of everything, something that
builds reliably on a number of build machine distros is what we really need.
Philip
next prev parent reply other threads:[~2011-11-17 14:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 22:07 Yocto usability questions Jeff Osier-Mixon
2011-11-16 23:39 ` Mark Hatle
2011-11-17 4:03 ` Ourada, Paul
2011-11-17 7:19 ` Koen Kooi
2011-11-17 13:06 ` Rainer Koenig
2011-11-17 14:25 ` Philip Balister [this message]
2011-11-17 21:38 ` Chris Tapp
2011-11-17 22:17 ` Brian Duffy
2011-11-17 23:19 ` Osier-mixon, Jeffrey
2011-11-18 9:40 ` Jack Mitchell
2011-11-18 15:02 ` Ourada, Paul
2011-11-18 15:42 ` Philip Balister
2011-11-18 15:56 ` Gary Thomas
2011-11-18 16:00 ` Philip Balister
2011-11-18 16:04 ` Gary Thomas
2011-11-18 16:56 ` Tom Rini
2011-11-18 16:56 ` Jack Mitchell
2011-11-18 17:20 ` Osier-mixon, Jeffrey
2011-11-18 19:40 ` Jeff Osier-Mixon
2011-11-18 20:12 ` Joshua Lock
2011-11-18 20:54 ` Tom Zanussi
2011-11-18 21:31 ` Osier-mixon, Jeffrey
2011-11-18 21:56 ` Chris Tapp
2011-11-18 22:32 ` Philip Balister
2011-11-18 22:36 ` Osier-mixon, Jeffrey
2011-11-22 12:52 ` Rainer Koenig
2011-11-22 15:23 ` Tom Zanussi
2011-11-22 16:49 ` Joshua Lock
2011-11-22 21:03 ` Chris Tapp
2011-11-22 22:52 ` Joshua Lock
-- strict thread matches above, loose matches on Subject: below --
2018-12-21 5:16 Prasenjit Mahanti
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=4EC5195F.5060302@balister.org \
--to=philip@balister.org \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=yocto@yoctoproject.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.