All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@openembedded.org
Subject: Re: Task-base is big :(
Date: Wed, 12 Sep 2007 14:45:21 +0200	[thread overview]
Message-ID: <46E7DF61.2AEEA36E@vollmann.ch> (raw)
In-Reply-To: HOECLKEKOHLAMMGDLLBHGENPMDAA.skoroneos@digital-opsis.com

Stelios Koroneos wrote:
> > Same here, but I guess we are using OE for similar purposes. Using
> > OpenEmbedded for embedded applications you build a kernel, need a
> > *few* packages (say 10) and some custom stuff (say 20 packages).
This is one usage we have, for specific projects.

> As more people start to use OE and as these people would be mostly
> interested in "vertical" solutions (develop an app or add apps to an
> existing distro without having to rebuild everything) i think we need to
> have a closer look at the OE SDK vs build everything from scratch.
Actually, for projects that are in a stage where they start to
build (internal) releases (that go to some test procedures),
building from scratch is important to be able to reproduce
these releases and apply some minor bugfixes to them.
But that doesn't mean that everything should be built from
scratch for each release (see me other mail on binary packages).
For packages used in these project I have no problems to put
in some effort to provide the packages in my overlay and tweak
some until they contain exactly what I need.

But we have always a number of project that just start to develop
or are still exploring their development options.
For those projects I try to provide "mini-distros" based
on existing distros (angstrom).  For these mini-distros
I prepare a feed that contains everything that builds and makes
sense for their hardware (so I mask everything related to
graphics and multimedia).

My current approach is to start with a big list of packages
setup a BBMASK and see what builds.  Those that don't build
I simply remove from my list or (if I think the package is
interesing enough) I try to modify that package in my
overlay so that it builds.

For such packages (for which I don't know whether they are ever
really used in any project) I'm a bit reluctant to put in much
effort, so I'd appreciate everything that makes my job here
easier.

> Having a "standard" toolchain availiable (and the way to use it) for people
> that are not interested in developing distro's would IMHO provide additional
> "user friendliness" and make OE an even more attractive solution.
Definitely.  But even for people like me (who provide some
infrastructure to a number of projcets inside a company or for
a given hardware) it would be nice to make "distro building"
easier.

  Detlef

-- 
Detlef Vollmann   vollmann engineering gmbh
Linux and C++ for Embedded Systems    http://www.vollmann.ch/



  parent reply	other threads:[~2007-09-12 12:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 11:18 Task-base is big :( Marcin Juszkiewicz
2007-09-11 17:37 ` Leon Woestenberg
2007-09-11 19:27   ` Koen Kooi
2007-09-11 21:10     ` USE flags - why they won't work for OE Richard Purdie
2007-09-11 23:14       ` Leon Woestenberg
2007-09-12  5:55         ` Stelios Koroneos
2007-09-12 11:06           ` José Bernardo Bandos Rodrigues
2007-09-12 16:38             ` Darcy Watkins
2007-09-12 11:46           ` Leon Woestenberg
2007-09-12 21:35             ` Richard Purdie
2007-09-11 21:17   ` Task-base is big :( Richard Purdie
2007-09-11 22:22     ` Detlef Vollmann
2007-09-11 22:55       ` Leon Woestenberg
2007-09-12  5:56         ` Stelios Koroneos
2007-09-12  7:53           ` Graeme Gregory
2007-09-12  8:43             ` Koen Kooi
2007-09-12 12:02             ` Binary packages (was: Task-base is big :( ) Detlef Vollmann
2007-09-12 12:45           ` Detlef Vollmann [this message]
2007-09-12 23:21           ` Task-base is big :( Richard Purdie
2007-09-11 23:43       ` Dr. Michael Lauer
2007-09-12  6:04         ` Koen Kooi
2007-09-14  7:21           ` Splitting up bluez in a sane way, was " Koen Kooi
2007-09-14  9:22             ` Marcin Juszkiewicz
2007-09-14  9:44               ` Koen Kooi
2007-09-15  8:29                 ` Koen Kooi
2007-09-15 12:31                   ` Marcin Juszkiewicz
2007-09-15 12:59                     ` Koen Kooi
2007-09-18 17:54                       ` Koen Kooi

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=46E7DF61.2AEEA36E@vollmann.ch \
    --to=dv@vollmann.ch \
    --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.