All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: How should OE be used?
Date: Mon, 24 Sep 2007 23:35:42 +0100	[thread overview]
Message-ID: <1190673342.19359.107.camel@localhost.localdomain> (raw)
In-Reply-To: <46F8280E.9050908@trolltech.com>

On Tue, 2007-09-25 at 07:11 +1000, Lorn Potter wrote:
> > Playing devil's advocate, take Poky, for example. A person can
> > download/check it out, edit one simple configuration file
> > (comment/uncomment lines), source a file and go :).
>
> This is ok for an individual with a known device, but for a company that 
> needs to produce their own distribution, for a new device, Poky is not a 
> choice.

I didn't make comment about Poky's suitability for anything. 

All I said is that its possible to produce a one stop configuration
process for OE which is as easy as your buildroot example. This proves
that its not some fundamental problem with OE, someone just needs to
implement it.

As for "for a company that needs to produce their own distribution, for
a new device, Poky is not a choice", thats just nonsense and our
experiences suggests otherwise ;-).

> _These_ are the people/companies that the OE/Foundation should also 
> be targeting to grow.

I think all agreed that OE wants to see more of these people/companies
using OE.

Cheers,

Richard





      reply	other threads:[~2007-09-24 22:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 21:24 How should OE be used? Philip Balister
2007-09-23 11:19 ` Leon Woestenberg
2007-09-23 12:33   ` Koen Kooi
2007-09-24 17:20     ` Tim Bird
2007-09-24 17:43       ` Koen Kooi
2007-09-24 18:01         ` Tim Bird
2007-09-24 15:55   ` Tim Bird
2007-09-24 16:35     ` Philip Balister
2007-09-24 17:14       ` Tim Bird
2007-09-24 18:04     ` Leon Woestenberg
2007-09-24 19:23       ` Koen Kooi
2007-09-24 14:48 ` Darcy Watkins
2007-09-25 12:19   ` Stelios Koroneos
2007-09-25 15:15     ` Koen Kooi
2007-09-25 20:54     ` Darcy Watkins
2007-09-24 16:14 ` Cliff Brake
2007-09-24 18:36 ` Craig Hughes
2007-09-24 19:27   ` Philip Balister
2007-09-24 21:37   ` Richard Purdie
2007-09-24 18:48 ` Lorn Potter
2007-09-24 19:01   ` Craig Hughes
2007-09-24 19:39     ` Lorn Potter
2007-09-24 20:33       ` Craig Hughes
2007-09-24 20:52   ` Richard Purdie
2007-09-24 21:11     ` Lorn Potter
2007-09-24 22:35       ` Richard Purdie [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=1190673342.19359.107.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.