From: Paul Sokolovsky <pmiscml@gmail.com>
To: Marcin Juszkiewicz <openembedded@hrw.one.pl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: What is task-base?
Date: Mon, 16 Oct 2006 01:02:22 +0300 [thread overview]
Message-ID: <161534574.20061016010222@gmail.com> (raw)
In-Reply-To: <200610151544.28474.openembedded@hrw.one.pl>
Hello Marcin,
Sunday, October 15, 2006, 4:44:27 PM, you wrote:
> Today I added few sections into org.openembedded.documentation repository.
> One of them was about task-base and is available here:
> http://www.openembedded.org/user-manual&dpage=ch04s04
> I also wrote on my blog some stuff about it:
> http://www.hrw.one.pl/2006/10/15/openembedded-documentation-day/
-----------
> TARGET_ARCH = "i686"
> IPKG_EXTRA_ARCHS = "x86 i386 i486 i586"
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-x86"
>
> MACHINE_FEATURES = "kernel26 pci alsa usbhost"
>
> require conf/machine/include/tune-athlonmp.conf
----------
If it can be made so clean, why do we have so tangled configs for
many machines, at least for PocketPC-based? Do we need more strict
policy of what goes into machine configs and about the order of
variables? For example, I doubt it's good idea to have IMAGE_FSTYPES
in machine configs - how that can be machine's property? It's just
adhoc preference of conf author, which hardly will work for someone
another, so really should be set in local.conf.
Also, it's good idea to group by some logical sections, for example,
machine properties rooted in hardware vs package selectors
(PREFERRED_PROVIDERs, etc) vs module autoload specification vs
something else.
> Have a nice reading.
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2006-10-15 22:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 21:46 What is task-base? Richard Purdie
2006-08-28 9:31 ` Marcin Juszkiewicz
2006-08-28 9:40 ` Koen Kooi
2006-09-01 14:18 ` Koen Kooi
2006-09-01 15:06 ` pHilipp Zabel
2006-09-27 12:27 ` Koen Kooi
2006-09-27 16:49 ` pHilipp Zabel
2006-09-27 17:01 ` Koen Kooi
2006-09-01 14:56 ` pHilipp Zabel
2006-09-01 15:10 ` Koen Kooi
2006-10-15 13:44 ` Marcin Juszkiewicz
2006-10-15 22:02 ` Paul Sokolovsky [this message]
2006-10-15 22:29 ` Koen Kooi
2006-10-16 2:24 ` Paul Sokolovsky
2006-10-16 7:17 ` Richard Purdie
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=161534574.20061016010222@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded@hrw.one.pl \
/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.