From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: static busybox?
Date: Fri, 3 Aug 2012 10:30:15 -0500 [thread overview]
Message-ID: <501BEE87.8080104@windriver.com> (raw)
In-Reply-To: <CAP9ODKpCdoe2G5q3Ly-qTYKvDsWNq6sypQq8QQ=dPO1=gRZSpA@mail.gmail.com>
On 8/3/12 6:19 AM, Otavio Salvador wrote:
> On Thu, Aug 2, 2012 at 7:50 PM, Stuart Yoder <b08248@gmail.com> wrote:
>> On Wed, Aug 1, 2012 at 3:05 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>> On Wed, Aug 1, 2012 at 4:05 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>>>> On 8/1/12 1:59 PM, McClintock Matthew-B29882 wrote:
>>>>> This is one approach, to change busybox completely for a specific
>>>>> added layer. But, what if we only want to make this change to busybox
>>>>> if the lxc recipe is included in the image? What about other packages
>>>>> also requesting changes?
>>>>
>>>> There is no method within OE to change a configuration of one item, if
>>>> another item is included or not.
>>>>
>>>> The way to do this is use the PACKAGECONFIG options, and then pass via a
>>>> per-recipe configuration if you want lxc support enabled or not.. (or
>>>> possible lxc becomes a distro flag?)
>>>
>>> For lxc specific case I think we can just have a recipe that sets the
>>> busybox' static option. It seems to be the only difference we'd have
>>> for it.
>>
>> Do you mean a distinct 'busybox-static' recipe that lxc would
>> depend on?
>
> Yes; it might include the regular busybox recipe and do the need
> appends, or something like that.
>
That would certainly be my recommendation. Use the same base recipe, same
configuration mechanism, and then just add the addition chunk(s) to the SRC_URI
and it should be much easier to maintain long-term.
The only thing remaining, is anyone working on adding the configuration yet?
(I'd love to, but I'm swamped with work for about the next 2-3 weeks.)
--Mark
prev parent reply other threads:[~2012-08-03 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 18:14 static busybox? Stuart Yoder
2012-07-31 19:36 ` McClintock Matthew-B29882
2012-07-31 20:01 ` Mark Hatle
2012-08-01 16:48 ` Darren Hart
2012-07-31 19:59 ` Mark Hatle
2012-07-31 20:02 ` Jack Mitchell
2012-07-31 20:07 ` Bruce Ashfield
2012-08-01 16:21 ` Stuart Yoder
2012-08-01 16:36 ` Mark Hatle
2012-08-01 16:49 ` Darren Hart
2012-08-01 16:52 ` Bruce Ashfield
2012-08-01 18:59 ` McClintock Matthew-B29882
2012-08-01 19:05 ` Mark Hatle
2012-08-01 20:05 ` Otavio Salvador
2012-08-02 22:50 ` Stuart Yoder
2012-08-03 10:20 ` Koen Kooi
2012-08-03 11:19 ` Otavio Salvador
2012-08-03 15:30 ` Mark Hatle [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=501BEE87.8080104@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox