From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: [PATCH] Update poky-feed-config-opkg to generate a useful package setup
Date: Fri, 02 Sep 2011 13:52:37 -0600 [thread overview]
Message-ID: <4E613405.8020509@mlbassoc.com> (raw)
In-Reply-To: <1314984886.5939.629.camel@rex>
On 2011-09-02 11:34, Richard Purdie wrote:
> On Fri, 2011-09-02 at 11:10 -0600, Gary Thomas wrote:
>> On 2011-09-02 11:04, Richard Purdie wrote:
>>> On Fri, 2011-09-02 at 10:46 -0600, Gary Thomas wrote:
>>>> The current poky-feed-config-opkg package only generates a skeleton for the
>>>> opkg setups. In particular, the base configuration file /etc/opkg/base-files.conf
>>>> is not filled in at all.
>>>>
>>>> The attached patch fills this file in, using variables set by the
>>>> user (local.conf, site.conf, etc). If left unset, the behaviour will
>>>> be the same as current.
>>>>
>>>> One thing I found is that opkg is very noisy if there are databases
>>>> mentioned in base-files.conf that don't exist. For example, on ARM
>>>> platforms, there are a large number of possibilities (arm, armv5, armv6, ...)
>>>> that are never populated in .../tmp/deploy/ipk. The changes to this
>>>> recipe will prune the file to only include those ipk databases which
>>>> have actual files present.
>>>
>>> Your code is one big race unfortunately since the actual file generated
>>> will depend on whether any packaging task has run before it or not (and
>>> what package type that was). I'm not sure how to fix that but it can't
>>> go in as it stands due to that...
>>
>> I agree :-) That's what these lines are for:
>> do_compile[depends] += "base-files:do_package"
>> do_compile[depends] += "virtual/kernel:do_package"
>>
>> They solve the problem for me, i.e. if I build an image which includes
>> this recipe from scratch, then the do_compile step is held off until
>> sufficient work has gone on to make the database useful.
>
> Sorry, I didn't see that on the bottom. I can't say I really like it. If
> you're going to do that you might as well just hardcode the list as:
>
> "all ${TUNE_PKGARCH} ${MACHINE}"
>
> ?
Yes, that would probably be equivalent. Would that be an acceptable change?
Bottom line though is that the recipe currently does nothing for the
end user and I was trying to make something that would work out of
the box for "Joe Average User"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-09-02 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 16:46 [PATCH] Update poky-feed-config-opkg to generate a useful package setup Gary Thomas
2011-09-02 17:04 ` Richard Purdie
2011-09-02 17:10 ` Gary Thomas
2011-09-02 17:34 ` Richard Purdie
2011-09-02 19:52 ` Gary Thomas [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=4E613405.8020509@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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.