From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Controlling package build ordering
Date: Mon, 14 Feb 2011 16:43:44 -0700 [thread overview]
Message-ID: <4D59BE30.9050802@mlbassoc.com> (raw)
I have a modified version of poky-feed-config-opkg which
actually builds an opkg database (as opposed to the default
which does not). I've set it so that my base-feeds.conf
only contains entries for valid package sets like this:
for arch in $ipkgarchs; do
# Only export real directories
if [ -d "${DEPLOY_DIR}/ipk/${arch}" ]; then
echo "src/gz ${FEEDNAMEPREFIX}-$arch ${FEEDURIPREFIX}/$arch" >> $basefeedconf
fi
done
As you can see, only those entries which have some packages
will be included.
The problem I have is _when_ my feed-config-opkg.bb is actually
built. If I start from scratch, it gets built pretty early and
the ipk tree is often quite empty, perhaps only containing
a single collection. If I rerun this at the end, say after
building a complete image, then I get a complete set of entries.
What I'd like to do is find a way to postpone the building of
this recipe until very late, hopefully just before the final
image is built.
Is there any way to fine tune the build and accomplish this?
Note: if I leave out the test for valid subdirectories it all
works but then I get errors at runtime complaining about the
empty collections. This is what I'd like to avoid.
Thanks for any ideas
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
reply other threads:[~2011-02-14 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D59BE30.9050802@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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.