From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Working with OEMs
Date: Mon, 08 Feb 2010 13:37:35 -0500 [thread overview]
Message-ID: <4B7059EF.8020607@balister.org> (raw)
In-Reply-To: <18e217241002080848t193add2drd5603d0c252ee509@mail.gmail.com>
On 02/08/2010 11:48 AM, C Michael Sundius wrote:
> - I find it a bit dishartening that Holger does not recommend you to use OE
> for software development. One of the main reasons we were in search for a
> comprehensive build system was so that we could offer a consistent means of
> buliding our entire distribution to all developers and Configurtion Mgmt,
> Testing, Release teams alike with out everyone having to be an expert with
> all parts of the system (and all different build tools that had cropped up
> in the different locations we have engineers - india, US east coast, west
> coast). It *is* difficult to make it work for devlopers and build teams
> alike, but having a consistent means building software is a huge step
> creating a really great build system. Further if people are discouraged from
> using OE as a tool for developers, then it will never get any better and
> this hole of support in OE will not be filled.
Another way of looking at Holder's response is that we feel we could do
a better job of supporting people using OE to do software development.
There are certainly ways to use OE to do SW development.
I would really like to see us look at improving the experience for
people doing sw dev for OE based distributions.
Philip
next prev parent reply other threads:[~2010-02-08 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 19:28 Working with OEMs Jeremy Grant
2010-02-06 19:12 ` Holger Hans Peter Freyther
2010-02-08 16:48 ` C Michael Sundius
2010-02-08 18:37 ` Philip Balister [this message]
2010-02-09 17:56 ` C Michael Sundius
2010-02-09 21:47 ` Michael Smith
2010-02-09 22:33 ` Peter Chubb
2010-02-09 23:23 ` C Michael Sundius
2010-02-09 23:01 ` C Michael Sundius
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=4B7059EF.8020607@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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.