From: Thomas Kunze <thommycheck@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Some beginners problems
Date: Fri, 12 Sep 2008 15:56:01 +0200 [thread overview]
Message-ID: <48CA74F1.3060306@gmx.de> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E2B3B05@hiob.intern.dresearch.de>
Sledz, Steffen wrote:
>>>>> I wan't to make an image (e.g. minimal-image) for atngw100
>>>>> but with different linux kernel configuration (e.g.
>>>>> CONFIG_EXT2_FS=y). What's th right way to do this?
>>>>>
>>>>> * Just edit packages/linux/linux-2.6.24/atngw100/defconfig?
>>>>>
>>>>>
>>>>
>>>> Yes. But don't forget to increase the PR. Otherwise bitbake
>>>> doesn't know that the recipe was changed and doesn't rebuild
>>>> it.
>>>>
>>>>
>>> The change is not a bug fix or something like this. It's
>>> just a variant and not mentioned to become committed. So if i
>>> increase PR and someone else fixes a bug and increases PR too
>>> and I pull this fixes from git I have a conflict. :(
>>>
>>>
>> Yes but you will always have this problem with local changes and it
>> shouldn't be too hard to resolve such conflicts.
>>
>
> Is it possible (and is it a good idea) to create a new distro (or a new machine) for such a purpose?
>
>
In oe a distro decides which versions of packages to use or which
providers to use (qtopia-x11 vs. qtopia-framebuffer for example.)
A machine decides which architecture/kernel etc you have. I don't see
how you could abuse that to guard against conflicts between
local changes and upstream changes.
> Or is it possible to set parameters in local.conf which are available in the package bbfile for evaluation?
>
This is possible but doesn't solve the problem imo.
You may want to look at bitbake-collections:
http://bec-systems.com/oe/html/special_bitbake_collections.html
http://www.pokylinux.org/doc/poky-handbook.html#usingpoky-changes-collections
as Javi Roman suggested. Maybe this is what you want. But I would push
everything upstream
that is pushable and fix conflicts for all other stuff as necessary.
next prev parent reply other threads:[~2008-09-12 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 10:26 Some beginners problems Sledz, Steffen
2008-09-12 10:46 ` Javi Roman
2008-09-12 10:47 ` Thomas Kunze
2008-09-12 11:05 ` Sledz, Steffen
2008-09-12 11:26 ` Thomas Kunze
2008-09-12 13:07 ` Sledz, Steffen
2008-09-12 13:56 ` Thomas Kunze [this message]
2008-09-12 19:01 ` Rich Pixley
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=48CA74F1.3060306@gmx.de \
--to=thommycheck@gmx.de \
--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.